Prioritization in Beam Failure Recovery Procedures

ABSTRACT

Beam failure recovery procedures (BFR) are described for wireless communications. At least one transmission for a BFR procedure may overlap with a scheduled transmission. A wireless device may prioritize a transmission for a BFR procedure, for example, by dropping the scheduled transmission and transmitting the at least one transmission the BFR procedure.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/669,473, titled “Prioritization in Beam Failure Recovery Procedure”and filed on May 10, 2018. The above-referenced application is herebyincorporated by reference in its entirety.

BACKGROUND

A base station and/or a wireless device may use a beam failure recovery(BFR) procedure based on detecting a beam failure. A BFR procedure mayinclude transmission of at least one control signal. The transmission ofthe at least one control signal, or other portion of the BFR procedure,may be unsuccessful and/or delayed, which may lead to undesireableoutcomes.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

BFR procedures are described. A wireless device may be configured for aBFR procedure based on configuration parameters transmitted by a basestation. A wireless device may transmit at least one signal tofacilitate BFR (e.g., a BFR request). For example, a wireless device maytransmit at least one signal to facilitate BFR based on the wirelessdevice detecting a beam failure. A wireless device may determine thatthe at least one signal for the BFR procedure overlaps with a scheduledtransmission on another channel. A wireless device may drop thescheduled transmission and transmit the at least one signal for the BFRprocedure, for example, if the wireless device determines that a controlchannel to be used for the transmission of the at least one signal forthe BFR procedure overlaps with the scheduled transmission. By droppingthe scheduled transmission and transmitting the at least one signal forthe BFR procedure, the wireless device may be able to complete the BFRprocedure successfully and/or with reduced delay.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A and FIG. 16B show examples of beam failure scenarios.

FIG. 17 shows an example of a beam failure recovery (BFR) procedure.

FIG. 18 shows an example of a request configuration for a BFR procedure.

FIG. 19 shows an example of a BFR procedure.

FIG. 20 shows an example of a BFR procedure.

FIG. 21A and FIG. 21B show examples of BFR procedures.

FIG. 22A and FIG. 22B show examples of BFR procedures.

FIG. 23 shows an example method of a BFR procedure by a wireless device.

FIG. 24 shows an example method for a BFR procedure by a base station.

FIG. 25 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto beam failure recovery procedures in multicarrier communicationsystems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BFR Beam Failure Recovery

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BSR Buffer Status Report

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCH Logical Channel

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Media Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission and Receiving Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs that indicate one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by SGC; paging for mobile terminateddata area managed by SGC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a SGC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signalling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g., AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel. A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time, as well asan example frame structure, for a carrier. A multicarrier OFDMcommunication system may include one or more carriers, for example,ranging from 1 to 32 carriers (such as for carrier aggregation) orranging from 1 to 64 carriers (such as for dual connectivity). Differentradio frame structures may be supported (e.g., for FDD and/or for TDDduplex mechanisms). FIG. 6 shows an example frame timing. Downlink anduplink transmissions may be organized into radio frames 601. Radio frameduration may be 10 milliseconds (ms). A 10 ms radio frame 601 may bedivided into ten equally sized subframes 602, each with a 1 ms duration.Subframe(s) may comprise one or more slots (e.g., slots 603 and 605)depending on subcarrier spacing and/or CP length. For example, asubframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHzsubcarrier spacing may comprise one, two, four, eight, sixteen andthirty-two slots, respectively. In FIG. 6, a subframe may be dividedinto two equally sized slots 603 with 0.5 ms duration. For example, 10subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in a 10 ms interval. Othersubframe durations such as, for example, 0.5 ms, 1 ms, 2 ms, and 5 msmay be supported. Uplink and downlink transmissions may be separated inthe frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols 604 in a slot 605 may depend on thecyclic prefix length. A slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may comprise downlink, uplink, and/or a downlink part and anuplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device.

The base station may transmit one or more RRC messages indicating aperiodicity of the CS grant. The base station may send (e.g., transmit)DCI via a PDCCH addressed to a CS -RNTI to activate the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message. The CS grant may beimplicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a preemption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a CORESETs for at least one common search space. Foroperation on the PCell, one or more higher layer parameters may indicateat least one initial UL BWP for a random access procedure. If a wirelessdevice is configured with a secondary carrier on a primary cell, thewireless device may be configured with an initial BWP for random accessprocedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station

CU and different combinations of lower protocol layers (e.g., RANfunctions) in base station DUs. A functional split may supportflexibility to move protocol layers between a base station CU and basestation DUs, for example, depending on service requirements and/ornetwork environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC_Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC_Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC_Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer. Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the S Cell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may flush HARQ buffers associated with the activatedSCell.

A wireless device may not perform certain operations, for example, if anSCell is deactivated. The wireless device may not perform one or more ofthe following operations if an SCell is deactivated: transmitting SRS onthe SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell;transmitting on UL-SCH on the SCell; transmitting on a RACH on theSCell; monitoring at least one first PDCCH on the SCell; monitoring atleast one second PDCCH for the SCell on the PCell; and/or transmitting aPUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

A base station may configure a wireless device with uplink (UL)bandwidth parts (BWPs) and downlink (DL) BWPs, for example, to enablebandwidth adaptation (BA) for a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., an SCell may not haveUL BWPS) to enable BA for an SCell, for example, if CA is configured.For the PCell, a first initial BWP may be a first BWP used for initialaccess. For the SCell, a second initial BWP may be a second BWPconfigured for the wireless device to first operate on the SCell if theSCell is activated.

A first DL and a first UL may switch BWP independently, for example, inpaired spectrum (e.g., FDD). A second DL and a second UL may switch BWPsimultaneously, for example, in unpaired spectrum (e.g., TDD). Switchingbetween configured BWPs may be based on DCI and/or an inactivity timer.An expiry of the inactivity timer associated with a cell may switch anactive BWP to a default BWP, for example, if the inactivity timer isconfigured for a serving cell. The default BWP may be configured by thenetwork.

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, in FDD systems configuredwith BA. One DL/UL BWP pair may be active at a time in an active servingcell, for example, in TDD systems. Operating on the one UL BWP and theone DL BWP (and/or the one DL/UL pair) may enable a wireless device touse a reasonable amount of power (e.g., reasonable battery consumption).BWPs other than the one UL BWP and the one DL BWP that the wirelessdevice may be configured with may be deactivated. The wireless devicemay refrain from monitoring a PDCCH, and/or may refrain fromtransmitting via a PUCCH, PRACH and/or UL-SCH, for example, ondeactivated BWPs.

A serving cell may be configured with a first number (e.g., four) ofBWPs. A wireless device and/or a base station may have one active BWP atany point in time, for example, for an activated serving cell. A BWPswitching for a serving cell may be used to activate an inactive BWPand/or deactivate an active BWP. The BWP switching may be controlled bya PDCCH indicating a downlink assignment or an uplink grant. The BWPswitching may be controlled by an inactivity timer (e.g.,bandwidthpartInactivityTimer). The BWP switching may be controlled by aMAC entity, for example, based on initiating a random access procedure.A BWP may be initially active without receiving a PDCCH indicating adownlink assignment or an uplink grant, for example, based on anaddition of an SpCell or an activation of an SCell. The active BWP for aserving cell may be indicated by an RRC message and/or a PDCCH message(e.g., PDCCH order). A DL BWP may be paired with an UL BWP, and/or BWPswitching may be common for both UL and DL, for example, for unpairedspectrum.

A MAC entity may use operations on an active BWP for an activatedserving cell configured with a BWP, such as one or more of: transmittingvia an UL-SCH; transmitting via a RACH; monitoring a PDCCH; transmittingvia a PUCCH; receiving via a DL-SCH; initializing and/or reinitializingsuspended configured uplink grants of configured grant Type 1 accordingto a stored configuration, if any and/or to start in a symbol based on aprocedure. On an inactive BWP for each activated serving cell configuredwith a BWP, a MAC entity: may refrain from transmitting via an UL-SCH,may refrain from transmitting via a RACH, may refrain from monitoring aPDCCH, may refrain from transmitting via a PUCCH, may refrain fromtransmitting an SRS, may refrain from receiving via a DL-SCH, may clearany configured downlink assignment and configured uplink grant ofconfigured grant Type 2, and/or may suspend any configured uplink grantof configured Type 1.

A MAC entity may perform a random access procedure (e.g., based on aninitiation of the random access procedure) on an active DL BWP and theactive UL BWP, for example, if PRACH resources are configured for theactive UL BWP. A MAC entity may switch to an initial DL BWP and aninitial UL BWP, for example, if PRACH resources are not configured foran active UL BWP (e.g., based on initiation of a random accessprocedure). The MAC entity may perform the random access procedure onthe initial DL BWP and the initial UL BWP, for example, based on the BWPswitching.

A wireless device may perform BWP switching to a BWP indicated by aPDCCH, for example, if a MAC entity receives a PDCCH (e.g., a PDCCHorder) for a BWP switching of a serving cell, for example, if a randomaccess procedure associated with this serving cell is not ongoing. Awireless device may determine whether to switch a BWP or ignore thePDCCH for the BWP switching, for example, if a MAC entity received aPDCCH for a BWP switching while a random access procedure is ongoing inthe MAC entity. The MAC entity may stop the ongoing Random Accessprocedure and initiate a second Random Access procedure on a newactivated BWP, for example, if the MAC entity decides to perform the BWPswitching. The MAC entity may continue with the ongoing Random Accessprocedure on the active BWP, for example if the MAC decides to ignorethe PDCCH for the BWP switching. A wireless device may perform the BWPswitching to a BWP indicated by the PDCCH, for example, if a MAC entityreceives a PDCCH for a BWP switching addressed to a C-RNTI for asuccessful completion of a Random Access procedure.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP for a variety of reasons. The MAC entity maystart or restart the BWP-InactivityTimer associated with the active DLBWP, for example, if one or more of the following occur: aBWP-InactivityTimer is configured for an activated serving sell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, if the Default-DL-BWP is not configured and theactive DL BWP is not the initial BWP; and/or if one or more of thefollowing occur: if a PDCCH addressed to C-RNTI or CS-RNTI indicatingdownlink assignment or uplink grant is received on the active BWP,and/or if there is not an ongoing random access procedure associatedwith the activated serving cell.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP, for example, if one or more of the followingoccur: if a BWP-InactivityTimer is configured for an activated servingcell, if a Default-DL-BWP is configured and an active DL BWP is not aBWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP is notconfigured and the active DL BWP is not the initial BWP; and/or if oneor more of the following occur: if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,and/or if there is not an ongoing random access procedure associatedwith the activated serving cell.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP, for example, if one or more of the followingoccur: if a BWP-InactivityTimer is configured for an activated servingcell, if a Default-DL-BWP is configured and an active DL BWP is not aBWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP is notconfigured and the active DL BWP is not the initial BWP; and/or if oneor more of the following occur: if a PDCCH addressed to C-RNTI orCS-RNTI indicating downlink assignment or uplink grant is received onthe active BWP, if a MAC-PDU is transmitted in a configured uplink grantor received in a configured downlink assignment, and/or if an ongoingrandom access procedure associated with the activated Serving Cell issuccessfully completed in response to receiving the PDCCH addressed to aC-RNTI.

The MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP based on switching the active BWP. For example,the MAC entity may start or restart the BWP-InactivityTimer associatedwith the active DL BWP if a PDCCH for BWP switching is received and thewireless device switches an active DL BWP to the DL BWP, and/or if oneor more of the following occur: if a default downlink BWP is configuredand the DL BWP is not the default downlink BWP, and/or if a defaultdownlink BWP is not configured and the DL BWP is not the initialdownlink BWP.

The MAC entity may stop the BWP-InactivityTimer associated with anactive DL BWP of the activated serving cell, for example, if one or moreof the following occur: if BWP-InactivityTimer is configured for anactivated serving cell, if the Default-DL-BWP is configured and theactive DL BWP is not the BWP indicated by the Default-DL-BWP, and/or ifthe Default-DL-BWP is not configured and the active DL BWP is not theinitial BWP; and/or if a random access procedure is initiated. The MACentity may stop a second BWP-InactivityTimer associated with a secondactive DL BWP of an SpCell, for example, if the activated Serving Cellis an SCell (other than a PSCell).

The MAC entity may perform BWP switching to a BWP indicated by theDefault-DL-BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if theDefault-DL-BWP is configured and the active DL BWP is not the BWPindicated by the Default-DL-BWP, if the Default-DL-BWP is not configuredand the active DL BWP is not the initial BWP, if BWP-InactivityTimerassociated with the active DL BWP expires, and/or if the Default-DL-BWPis configured. The MAC entity may perform BWP switching to the initialDL BWP, for example, if the MAC entity may refrain from performing BWPswitching to a BWP indicated by the Default-DL-BWP.

A wireless device may be configured for operation in BWPs of a servingcell. The wireless device may be configured by higher layers for theserving cell for a set of (e.g., four) bandwidth parts (BWPs) forreceptions by the wireless device (e.g., DL BWP set) in a DL bandwidthby a parameter (e.g., DL-BWP). The wireless device may be configuredwith a set of (e.g., four) BWPs for transmissions by the wireless device(e.g., UL BWP set) in an UL bandwidth by a parameter (e.g., UL-BWP) forthe serving cell. An initial active DL BWP may be determined, forexample, by: a location and number of contiguous PRBs; a subcarrierspacing; and/or a cyclic prefix (e.g., for the control resource set fora Type0-PDCCH common search space). A wireless device may be provided(e.g., by a higher layer) a parameter (e.g., initial-UL-BWP) for aninitial active UL BWP for a random access procedure, for example, foroperation on a primary cell. The wireless device may be provided (e.g.,by a higher layer) a parameter (e.g., Active-BWP-DL-Pcell) for firstactive DL BWP for receptions, for example, if a wireless device has adedicated BWP configuration. The wireless device may be provided (e.g.,by a higher layer) a parameter (e.g., Active-BWP-UL-Pcell) for a firstactive UL BWP for transmissions on a primary cell, for example, if awireless device has a dedicated BWP configuration.

The wireless device may be configured with a variety of parameters for aDL BWP and/or for an UL BWP in a set of DL BWPs and/or UL BWPs,respectively, for a serving cell. The wireless device may be configuredwith one or more of: a subcarrier spacing (e.g., provided by higherlayer parameter DL-BWP-mu or UL-BWP-mu), a cyclic prefix (e.g., providedby higher layer parameter DL-BWP-CP or UL-BWP-CP), a PRB offset withrespect to the PRB (e.g., determined by higher layer parametersoffset-pointA-low-scs and ref-scs) and a number of contiguous PRBs(e.g., provided by higher layer parameter DL-BWP-BW or UL-BWP-BW), anindex in the set of DL BWPs or UL BWPs (e.g., by respective higher layerparameters DL-BWP-index or UL-BWP-index), a DCI format 1_0 or DCI format1_1 detection to a PDSCH reception timing values (e.g., provided byhigher layer parameter DL-data-time-domain), a PDSCH reception to aHARQ-ACK transmission timing values (e.g., provided by higher layerparameter DL-data-DL-acknowledgement), and/or a DCI 0_0 or DCI 0_1detection to a PUSCH transmission timing values (e.g., provided byhigher layer parameter UL-data-time-domain).

A DL BWP from a set of configured DL BWPs (e.g., with an index providedby higher layer parameter DL-BWP-index) may be paired with an UL BWPfrom a set of configured UL BWPs (e.g., with an index provided by higherlayer parameter UL-BWP-index). A DL BWP from a set of configured DL BWPsmay be paired with an UL BWP from a set of configured UL BWPs, forexample, if the DL BWP index and the UL BWP index are equal (e.g., forunpaired spectrum operation). A wireless device may not be expected toreceive a configuration where the center frequency for a DL BWP isdifferent from the center frequency for an UL BWP, for example, if theDL-BWP-index of the DL BWP is equal to the UL-BWP-index of the UL BWP(e.g., for unpaired spectrum operation).

A wireless device may be configured with CORESETs for every type ofcommon search space and/or for wireless device-specific search space,for example, for a DL BWP in a set of DL BWPs on a primary cell. Thewireless device may not be expected to be configured without a commonsearch space on the PCell, or on the PSCell, in the active DL BWP. Thewireless device may be configured with control resource sets for PUCCHtransmissions, for example, for an UL BWP in a set of UL BWPs. Awireless device may receive a PDCCH message and/or a PDSCH message in aDL BWP, for example, according to a configured subcarrier spacing and/ora CP length for the DL BWP. A wireless device may transmit via a PUCCHand/or via a PUSCH in an UL BWP, for example, according to a configuredsubcarrier spacing and CP length for the UL BWP.

The BWP indicator field value may indicate an active DL BWP, from theconfigured DL BWP set, for DL receptions, for example, if a BWPindicator field is configured in DCI format 1_1. The BWP indicator fieldvalue may indicate the active UL BWP, from the configured UL BWP set,for UL transmissions. A wireless device may be provided (e.g., for theprimary cell) with a higher layer parameter (e.g., Default-DL-BWP, orany other a default DL BWP among the configured DL BWPs), for example,if a BWP indicator field is configured in DCI format 0_1. The defaultBWP may be the initial active DL BWP, for example, if a wireless deviceis not provided a default DL BWP by higher layer parameterDefault-DL-BWP. A wireless device may be expected to detect a DCI format0_1 indicating active UL BWP change, or a DCI format 1_1 indicatingactive DL BWP change, for example, if a corresponding PDCCH is receivedwithin first 3 symbols of a slot.

A wireless device may be provided (e.g., for a primary cell) with ahigher layer parameter (e.g., Default-DL-BWP, or any other a default DLBWP among the configured DL BWPs). The default DL BWP may be the initialactive DL BWP, for example, if a wireless device is not provided adefault DL BWP by the higher layer parameter Default-DL-BWP. A wirelessdevice may be provided with a higher layer parameter (e.g.,BWP-InactivityTimer) for a timer value for the primary cell. Thewireless device may increment the timer, if running, every interval of 1millisecond for frequency range 1, every 0.5 milliseconds for frequencyrange 2, or any other interval, for example, if the wireless device maynot detect a DCI format 1_1 for paired spectrum operation or, forexample, if the wireless device may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

Wireless device procedures on the secondary cell may be same as on theprimary cell. Wireless device procedures may use the timer value for thesecondary cell and the default DL BWP for the secondary cell, forexample, if a wireless device is configured for a secondary cell with ahigher layer parameter (e.g., Default-DL-BWP) indicating a default DLBWP among the configured DL BWPs and the wireless device is configuredwith a higher layer parameter (e.g., BWP-InactivityTimer) indicating atimer value. The wireless device may use the indicated DL BWP and theindicated UL BWP on the secondary cell as the respective first active DLBWP and first active UL BWP on the secondary cell or carrier, forexample, if a wireless device is configured by a higher layer parameter(e.g., Active-BWP-DL-SCell) for a first active DL BWP and by a higherlayer parameter (e.g., Active-BWP-UL-SCell) for a first active UL BWP ona secondary cell or carrier.

A wireless device may not be expected to transmit (e.g., for pairedspectrum operation) HARQ-ACK via a PUCCH resource indicated by a DCIformat 1_0 or a DCI format 1_1, for example, if the wireless devicechanges its active UL BWP on a PCell between a time of a detection ofthe DCI format 1_0 or the DCI format 1_1 and a time of a correspondingHARQ-ACK transmission on the PUCCH.A wireless device may not be expectedto monitor a PDCCH if the wireless device performs radio resourcemanagement (RRM) measurements over a bandwidth that is not within theactive DL BWP for the wireless device.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RBs in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; anRB allocation; a time resource allocation; a bandwidth part indicator; aHARQ process number; one or more MCS; one or more NDI; one or more RV;MIMO related information; a downlink assignment index (DAI); a TPC forPUCCH; an SRS request; and/or padding (e.g., if necessary). The MIMOrelated information may comprise at least one of: a PMI; precodinginformation; a transport block swap flag; a power offset between PDSCHand a reference signal; a reference-signal scrambling sequence; a numberof layers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; anRB allocation; a time resource allocation; an MCS; an NDI; a phaserotation of the uplink DMRS; precoding information; a CSI request; anSRS request; an uplink index/DAI; a TPC for PUSCH; and/or padding (e.g.,if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the

DCI via a PDCCH. The base station may perform CRC scrambling by binarilyadding multiple bits of at least one wireless device identifier (e.g.,C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSIC-RNTI, and/or TPC-SRS-RNTI) on the CRC bits of the DCI. The wirelessdevice may check the CRC bits of the DCI, for example, if detecting theDCI. The wireless device may receive the DCI, for example, if the CRC isscrambled by a sequence of bits that is the same as the at least onewireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH in differentCORESETs, for example, to support a wide bandwidth operation. A basestation may transmit one or more RRC messages comprising configurationparameters of one or more CORESETs. A CORESET may comprise at least oneof: a first OFDM symbol; a number of consecutive OFDM symbols; a set ofresource blocks; and/or a CCE-to-REG mapping. A base station may send(e.g., transmit) a PDCCH in a dedicated CORESET for particular purpose,for example, for beam failure recovery confirmation. A wireless devicemay monitor a PDCCH for detecting DCI in one or more configuredCORESETs, for example, to reduce the power consumption.

A base station and/or a wireless device may have multiple antennas, forexample, to support a transmission with high data rate (such as in an NRsystem). A wireless device may perform one or more beam managementprocedures, as shown in FIG. 9B, for example, if configured withmultiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, for example, if at least a beam failureoccurs. A beam failure may occur if a quality of beam pair link(s) of atleast one PDCCH falls below a threshold. The threshold comprise be anRSRP value (e.g., −140 dbm, −110 dbm, or any other value) and/or a SINRvalue (e.g., −3 dB, −1 dB, or any other value), which may be configuredin a RRC message.

FIG. 16A shows an example of a first beam failure event. A base station1602 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 1601 from a TRP. The basestation 1602 and the wireless device 1601 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 1602 and the Rxbeam of the wireless device 1601) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 1603, a building, or any other obstruction).

FIG. 16B shows an example of a second beam failure event. A base stationmay send (e.g., transmit) a PDCCH from a beam to a wireless device 1611from a first TRP 1614. The base station and the wireless device 1611 maystart a beam failure recovery procedure on a new beam on a second TRP1612, for example, if the PDCCH on the beam is blocked (e.g., by amoving vehicle 1613, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pairlinks simultaneously, where M≥1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFR signal on an uplinkphysical channel to a base station, for example, if starting a BFRprocedure. The base station may send (e.g., transmit) DCI via a PDCCH ina CORESET, for example, after or in response to receiving the BFR signalon the uplink physical channel. The wireless may determine that the BFRprocedure is successfully completed, for example, after or in responseto receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting the BFR signal, for example, if the wireless device isconfigured with multiple resources for a BFR signal. The wireless devicemay select a BFR-PRACH resource for transmitting a BFR signal, forexample, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFR signal, for example, ifthe wireless device is configured with a BFR-PRACH resource, a BFR-PUCCHresource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFR signals. Theresponse may comprise the CRI associated with the candidate beam thatthe wireless device may indicate in the one or multiple BFR signals.

A base station may configure a wireless device with one or moreTCI-States using and/or via higher layer signaling. A number (e.g.,quantity, plurality, etc.) of the one or more TCI-States may depend on acapability of the wireless device. The wireless device may use the oneor more TCI-States to decode a PDSCH based on a detected PDCCH. Each ofthe one or more TCI-States state may include one RS setTCI-RS-SetConfig. The one RS set TCI-RS-SetConfig may contain one ormore parameters. The one or more parameters may be used, for example, toconfigure quasi co-location relationship between one or more referencesignals in the RS set and the DM-RS port group of the PDSCH. The one RSset may contain a reference to either one or two DL RSs and anassociated quasi co-location type (QCL-Type) for each one as configuredby the higher layer parameter QCL-Type. QCL-Types associated with two DLRSs may not necessarily be the same, for example, if the one RS setcontains a reference to the two DL RSs. The references of the two DL RSsmay be, for example, to a same DL RS or to different DL RSs. TheQCL-Types indicated to the wireless device may be based on a higherlayer parameter QCL-Type. The higher layer parameter QCL-Type may takeone or a combination of the following types: QCL-TypeA′: {Doppler shift,Doppler spread, average delay, delay spread}, QCL-TypeB′: {Dopplershift, Doppler spread}, QCL-TypeC′: {average delay, Doppler shift} andQCL-TypeD′: {Spatial Rx parameter}.

A wireless device may receive an activation command. The activationcommand may be used to map one or more TCI states to one or morecodepoints of a TCI field in DCI. The wireless device may assume thatone or more antenna ports of one DM-RS port group of a PDSCH of aserving cell are spatially quasi co-located with an SSB, for example,(i) before the wireless device receives the activation command and/or(ii) after the wireless device receives a higher layer configuration ofTCI-States. The SSB may be determined in an initial access procedurewith respect to one or more of a Doppler shift, a Doppler spread, anaverage delay, a delay spread, and spatial Rx parameters, whereapplicable.

A wireless device may be configured by a base station, with a higherlayer parameter TCI-PresentInDCI. If the higher layer parameterTCI-PresentInDCI is set as ‘Enabled’ for a CORESET scheduling a PDSCH,the wireless device may assume that a TCI field is present in a DL DCIof a PDCCH transmitted on the CORESET. If the higher layer parameterTCI-PresentInDCI is set as ‘Disabled’ for a CORESET scheduling a PDSCHor if the PDSCH is scheduled by a DCI format 1_0 the wireless device mayassume, for determining PDSCH antenna port quasi co-location, that a TCIstate for the PDSCH is identical to the TCI state applied for theCORESET used for the PDCCH transmission.

The wireless device may use one or more TCI-States according to a valueof a TCI field in a detected PDCCH with DCI for determining PDSCHantenna port quasi co-location if the higher layer parameterTCI-PresentInDCI is set as ‘Enabled’. The wireless device may assumethat antenna ports of one DM-RS port group of a PDSCH of a serving cellare quasi co-located with one or more RS(s) in an RS set with respect toQCL type parameter(s) given by the indicated TCI state if a time offsetbetween the reception of the DL DCI and the corresponding PDSCH is equalto or greater than a threshold Threshold-Sched-Offset. The threshold maybe based on, for example, wireless device capability. The wirelessdevice may assume that antenna ports of one DM-RS port group of a PDSCHof a serving cell are quasi co-located based on a TCI state used forPDCCH quasi co-location indication of the lowest CORESET-ID in thelatest slot in which one or more CORESETs are configured for thewireless device, if (i) the offset between reception of the DL DCI andthe corresponding PDSCH is less than a threshold Threshold-Sched-Offsetand/or if (ii) the higher layer parameter TCI-PresentInDCI=‘Enabled’ orthe higher layer parameter TCI-PresentInDCI=‘Disabled’. The wirelessdevice may obtain the other QCL assumptions from the indicated TCIstates for its scheduled PDSCH, irrespective of a time offset betweenthe reception of the DL DCI and the corresponding PDSCH, if allconfigured TCI states do not contain QCL-TypeD′.

A base station and/or a wireless device may perform one or more beammanagement procedures, for example, if the base station and/or thewireless device are configured with multiple beams (e.g., in system suchas in an NR system). The wireless device may perform a BFR procedure(e.g., send one or more BFR signals), for example, if one or more beampair links between the base station and the wireless device fail.

A wireless device may receive one or more RRC messages that comprise BFRparameters. The one or more RRC messages may comprise one or more of anRRC connection reconfiguration message, an RRC connectionreestablishment message, and/or an RRC connection setup message. Thewireless device may detect at least one beam failure according to atleast one of BFR parameters and trigger a BFR procedure. The wirelessdevice may start a first timer, if configured, in response to detectingthe at least one beam failure. The wireless device may select a beam(e.g., a selected beam) in response to detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., determined based on RSRP, SINR, or BLER, etc.) from a set ofcandidate beams. The set of candidate beams may be identified by a setof reference signals (e.g., SSBs, or CSI-RSs). The wireless device maytransmit at least a first BFR signal to a base station in response toselecting the selected beam. The at least first BFR signal may beassociated with the selected beam. The at least first BFR signal may be,for example, a preamble transmitted on a PRACH resource, or an SR signaltransmitted on a PUCCH resource, or a beam indication transmitted on aPUCCH/PUSCH resource. The wireless device may transmit the at leastfirst BFR signal with a transmission beam corresponding to a receivingbeam associated with the selected beam. The wireless device, may, forexample, determine transmission beam by using the RF and/or digitalbeamforming parameters corresponding to the receiving beam. The wirelessdevice may start a response window in response to transmitting the atleast first BFR signal. The response window may be tracked using, forexample, a timer with a value configured by the base station. Thewireless device may monitor a PDCCH in a first CORESET while theresponse window is running. The first CORESET may be associated with theBFR procedure. The wireless device may monitor the PDCCH in the firstCORESET in condition of transmitting the at least first BFR signal. Thewireless device may receive a first DCI via the PDCCH in the firstCORESET while the response window is running. The wireless device mayconsider the BFR procedure successfully completed if the wireless devicereceives the first DCI via the PDCCH in the first CORESET before theresponse window expires. The wireless device may stop the first timer,if configured, if the BFR procedure is successfully completed.

The wireless device may increment a transmission number if a responsewindow expires and if the wireless device does not receive a DCI. Thetransmission number is initialized, for example, to a first number(e.g., 0) before a BFR procedure is triggered. If the transmissionnumber indicates a number less than a configured maximum transmissionnumber, the wireless device may repeat one or more actions comprising atleast one of: a BFR signal transmission, starting a response window,monitoring a PDCCH, and incrementing the transmission number if noresponse received during the response window is running. If thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device maydetermine that the BFR procedure was unsuccessful.

A wireless device may trigger an SR for requesting a UL-SCH resource,for example, if the wireless device has a new transmission. A basestation may transmit, to a wireless device, at least one messagecomprising parameters indicating zero, one, or more SR configurations.An SR configuration may comprise a set of PUCCH resources for SRs on oneor more BWPs, and/or one or more cells. A PUCCH resource (e.g., at mostone PUCCH resource) for an SR may be configured on a BWP (e.g., oneBWP). Each SR configuration may correspond to one or more logicalchannels. Each logical channel may be mapped to zero or one SRconfiguration configured by the at least one message. An SRconfiguration of a logical channel (LCH) that triggers a buffer statusreport (BSR) may be considered, for example, as a corresponding SRconfiguration for a triggered SR.

The at least one message may further comprise, for each SRconfiguration, one or more parameters indicating at least one of: an SRprohibit timer, a maximum number of SR transmissions, a parameterindicating a periodicity and an offset of an SR transmission, and/or aPUCCH resource. The SR prohibit timer may be, for example, a durationduring which the wireless device may be not allowed to transmit the SR.The maximum number of SR transmission may be, for example, a maximumnumber of SR transmissions that are allowed for the wireless device.

A PUCCH resource may be identified by one or more of at least: afrequency location (e.g., a starting PRB), a PUCCH format associatedwith an initial cyclic shift of a base sequence, and a time domainlocation (e.g., a starting symbol index). A PUCCH format may be, forexample, one of a PUCCH format 0, a PUCCH format 1, a PUCCH format 2, aPUCCH format 3, and/or a PUCCH format 4. A PUCCH format 0 may occupy 1or 2 OFDM symbols and is less than or equal to 2 bits. A PUCCH format 1may occupy between 4 and 14 OFDM symbols and is less than or equal to 2bits. A PUCCH format 2 may occupy 1 or 2 OFDM symbols and is greaterthan 2 bits. A PUCCH format 3 may occupy between 4 and 14 OFDM symbolsand is greater than 2 bits. A PUCCH format 4 may occupy between 4 and 14OFDM symbols and is greater than 2 bits.

A PUCCH format for an SR transmission may be a PUCCH format 0, or aPUCCH format 1. A wireless device may transmit a PUCCH in a PUCCHresource for a corresponding SR configuration, for example, only if thewireless device transmits a positive SR. For a positive SR transmissionusing PUCCH format 0, a wireless device may transmit a PUCCH by settinga cyclic shift to a first value (e.g., 0). For a positive SRtransmission using PUCCH format 1, a wireless device may transmit aPUCCH by setting a first bit, before BPSK modulation on a sequence, to afirst value (e.g., 0).

An SR may be multiplexed, for example, with a HARQ-ACK or a CSI on aPUCCH format. A wireless device may decide a cyclic shift of a basesequence based on the initial cyclic shift and a first cyclic shiftbased on one or more values of one or more HARQ-ACK bits, if a positiveSR is multiplexed with an HARQ-ACK. A wireless device may decide acyclic shift of the base sequence based on the initial cyclic shift anda second cyclic shift based on one or more values of the one or moreHARQ-ACK bits, if a negative SR is multiplexed with HARQ-ACK. The firstcyclic shift may be different from the second cyclic shift.

A wireless device may maintain an SR transmission counter (e.g., anSR_COUNTER) associated with an SR configuration. A wireless device mayset the SR_COUNTER of the SR configuration to a first value (e.g., 0) ifan SR of an SR configuration is triggered, and there are no other SRspending corresponding to the same SR configuration.

A wireless device may consider a triggered SR pending until it iscancelled. All pending SR(s) may be cancelled, for example, if one ormore UL grants accommodate all pending data available for transmission.

A wireless device may determine one or more PUCCH resources on an activeBWP as valid PUCCH resources at a time of an SR transmission occasion. Awireless device may transmit a PUCCH in a PUCCH resource associated withan SR configuration if the wireless device transmits a positive SR. Awireless device may transmit the PUCCH using PUCCH format 0, or PUCCHformat 1, according to a PUCCH configuration.

FIG. 17 shows an example of a BFR procedure. In some communicationsystems, a wireless device may stop a BWP inactivity timer if a randomaccess procedure is initiated, and/or the wireless device may restartthe BWP inactivity timer if the random access procedure is successfullycompleted (e.g., based on or in response to receiving DCI addressed to aC-RNTI of the wireless device). At step 1700, a wireless device mayreceive one or more RRC messages comprising BFR parameters. At step1702, the wireless device may detect at least one beam failure accordingto at least one BFR parameter. The wireless device may start a firsttimer, if configured, based on detecting the at least one beam failure.At step 1704, the wireless device may select a beam (e.g., a selectedbeam) based on detecting the at least one beam failure. The selectedbeam may be a beam with good channel quality (e.g., based on RSRP, SINR,and/or BLER) that may be selected from a set of candidate beams. Thecandidate beams may be indicated by a set of reference signals (e.g.,SSBs, or CSI-RSs). At step 1706, the wireless device may send (e.g.,transmit) at least a first BFR signal to a base station, for example,based on selecting the beam (e.g., selected beam). The at least firstBFR signal may be associated with the selected beam. The wireless devicemay send (e.g., transmit) the at least first BFR signal with atransmission beam corresponding to a receiving beam associated with theselected beam. The at least first BFR signal may be a preamble sent(e.g., transmitted) via a PRACH resource, an SR signal sent (e.g.,transmitted) via a PUCCH resource, a beam failure recovery signal sent(e.g., transmitted) via a PUCCH resource, and/or a beam report sent(e.g., transmitted) via a PUCCH and/or PUSCH resource. At step 1708, thewireless device may start a response window, for example, based onsending (e.g., transmitting) the at least first BFR signal. The responsewindow may be associated with a timer with a value configured by thebase station. The wireless device may monitor a PDCCH in a firstCORESET, for example, if the response window is running. The firstCORESET may be configured by the BFR parameters (e.g., RRC). The firstCORESET may be associated with the BFR procedure. The wireless devicemay monitor the PDCCH in the first CORESET in condition of transmittingthe at least first BFR signal.

At step 1710, the wireless device may detect (e.g., receive) a first DCIvia the PDCCH in the first CORESET, for example, if the response windowis running. At step 1712, the wireless device may determine that the BFRprocedure has successfully completed, for example, if the wirelessdevice receives the first DCI via the PDCCH in the first CORESET beforethe response window expires. The wireless device may stop the firsttimer, if configured, based on the BFR procedure successfully beingcompleted. The wireless device may stop the response window, forexample, based on the BFR procedure successfully being completed. If theresponse window expires, and the wireless device does not receive theDCI (e.g., at step 1710), the wireless device may, at step 1714,increment a transmission number. The transmission number may beinitialized to a first number (e.g., 0) before the BFR procedure istriggered. At step 1714, if the transmission number indicates a numberless than the configured maximum transmission number, the wirelessdevice may repeat one or more actions (e.g., at step 1704). The one ormore actions to be repeated may comprise at least one of a BFR signaltransmission, starting the response window, monitoring the PDCCH, and/orincrementing the transmission number, for example, if no responsereceived during the response window is running. At step 1716, if thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC message,for example, for a beam failure recovery procedure. The beam failurerecovery procedure may be used for indicating to a serving base stationof a new synchronization signal block (SSB) and/or CSI-RS, for example,if a beam failure is detected. The beam failure may be detected on oneor more serving SSB(s) and/or CSI-RS(s) of the serving base station. Thebeam failure may be detected by counting a beam failure instanceindication from a lower layer of the wireless device (e.g., PHY layer)to the MAC entity.

An RRC message may configure a wireless device with one or moreparameters (e.g., in BeamFailureRecoveryConfig) for a beam failuredetection and recovery procedure. The one or more parameters maycomprise one or more of: beamFailureInstanceMaxCount for a beam failuredetection, beamFailureDetectionTimer for the beam failure detection, anRSRP threshold (e.g., beamFailureCandidateBeamThreshold) for a beamfailure recovery, preamblePowerRampingStep for the beam failurerecovery, preambleReceivedTargetPower for the beam failure recovery,preambleTxMax for the beam failure recovery, and/or ra-ResponseWindow.The ra-ResponseWindow may be a time window to monitor one or moreresponses for the beam failure recovery using a contention-free RApreamble.

A wireless device may use at least one wireless device variable for abeam failure detection. BFI_COUNTER may be one of the at least onewireless device variable. The BFI_COUNTER may be a counter for a beamfailure instance indication. The BFI_COUNTER may be initially set tozero. The wireless device may start or restartbeamFailureDetectionTimer, for example, if a MAC entity of a wirelessdevice receives a beam failure instance indication from a lower layer(e.g., PHY) of the wireless device. The wireless device may incrementBFI_COUNTER, for example, in addition to starting or restarting thebeamFailureDetectionTimer. The wireless device may initiate a randomaccess procedure (e.g., on an SpCell) based on the BFI_COUNTER beingequal to beamFailureInstanceMaxCount+1. The wireless device may use theone or more parameters in the BeamFailureRecoveryConfig, for example,based on the initiating the random access procedure. The wireless devicemay set the BFI_COUNTER to zero, for example, if thebeamFailureDetectionTimer expires. The wireless device may determinethat the beam failure recovery procedure has successfully completed, forexample, if the random access procedure is successfully completed.

A MAC entity may start ra-ResponseWindow at a first PDCCH occasion fromthe end of the transmitting the contention-free random access preamble,for example, if a MAC entity of a wireless device sends (e.g.,transmits) a contention-free random access preamble for a BFRprocedure). The ra-ResponseWindow may be configured inBeamFailureRecoveryConfig. The wireless device may monitor at least onePDCCH (e.g., of an SpCell) for a response to the beam failure recoveryrequest, for example, if the ra-ResponseWindow is running. The beamfailure recovery request may be identified by a C-RNTI. The wirelessdevice may determine that a random access procedure has successfullycompleted, for example, if a MAC entity of a wireless device receives,from a lower layer of the wireless device, a notification of a receptionof at least one PDCCH transmission, and if the at least one PDCCHtransmission is addressed to a C-RNTI, and/or if a contention-freerandom access preamble for a beam failure recovery request istransmitted by the MAC entity.

A wireless device may initiate a contention-based random access preamblefor a beam failure recovery request. A MAC entity of the wireless devicemay start ra-ContentionResolutionTimer, for example, if the wirelessdevice transmits Msg3. The ra-ContentionResolutionTimer may beconfigured by RRC. Based on the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH if the ra-ContentionResolutionTimer is running. The wirelessdevice may consider the random access procedure successfully completed,for example, if the MAC entity receives, from a lower layer of thewireless device, a notification of a reception of the at least one PDCCHtransmission, if a C-RNTI MAC-CE is included in the Msg3, if a randomaccess procedure is initiated for a beam failure recovery, and/or the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice. The wireless device may stop the ra-ContentionResolutionTimer,for example, based on the random access procedure being successfullycompleted. The wireless device may determine that the beam failurerecovery has successfully completed, for example, if a random accessprocedure of a beam failure recovery is successfully completed.

A wireless device may be configured (e.g., for a serving cell) with afirst set of periodic CSI-RS resource configuration indexes by a higherlayer parameter (e.g., Beam-Failure-Detection-RS-ResourceConfig). Thewireless device may be configured with a second set of CSI-RS resourceconfiguration indexes and/or SS/PBCH block indexes by a higher layerparameter (e.g., Candidate-Beam-RS-List). The first set of CSI-RSresource configuration indexes and/or SS/PBCH block indexes and/or thesecond set of CSI-RS resource configuration indexes and/or SS/PBCH blockindexes may be used for radio link quality measurements on the servingcell. The wireless device may determine a first set to include SS/PBCHblock indexes and periodic CSI-RS resource configuration indexes, forexample, if a wireless device is not provided with higher layerparameter Beam-Failure-Detection-RS-ResourceConfig. The SS/PBCH blockindexes and the periodic CSI-RS resource configuration indexes maycomprise the same values as one or more RS indexes in one or more RSsets. The one or more RS indexes in the one or more RS sets may beindicated by one or more TCI states. The one or more TCI states may beused for respective control resource sets for which the wireless devicemay be configured to monitor a PDCCH. The wireless device may expect asingle port RS in the first set.

A first threshold (e.g., Qout,LR) may correspond to a first defaultvalue of a first higher layer parameter (e.g.,RLM-IS-OOS-thresholdConfig). A second threshold (e.g., Qin,LR) maycorrespond to a second default value of a higher layer parameter (e.g.,Beam-failure-candidate-beam-threshold). A physical layer in the wirelessdevice may compare a first radio link quality according to the first setof periodic CSI-RS resource configurations with the first threshold. Forthe first set, the wireless device may assess the first radio linkquality based on periodic CSI-RS resource configurations or SS/PBCHblocks. The periodic CSI-RS resource configurations and/or the SS/PBCHblocks may be associated (e.g., quasi co-located) with at least oneDM-RS of a PDCCH that may be monitored by the wireless device. Thewireless device may apply the second threshold to a first L1-RSRP forSS/PBCH blocks. The wireless device may apply the second threshold to asecond L1-RSRP for periodic CSI-RS resources, for example after scalinga respective CSI-RS reception power with a value provided by a higherlayer parameter (e.g., Pc_SS).

A physical layer in a wireless device may, for example, in slots forwhich the first radio link quality according to the first set isassessed, provide an indication to higher layers (e.g., MAC layer). Thewireless device may provide an indication to higher layers, for example,if the first radio link quality for all corresponding resourceconfigurations in the first set is less than the first threshold. Thewireless device may use the corresponding resource configurations in thefirst set to assess the first radio link quality. The physical layer mayinform the higher layers (e.g., MAC, RRC), for example, if the firstradio link quality is less than the first threshold with a firstperiodicity. The first periodicity may be determined by a maximum of theshortest periodicity of periodic CSI-RS configurations or SS/PBCH blocksin the first set and a time value (e.g., 2 ms or any other duration).Based on a request from higher layers (e.g., MAC layer), a wirelessdevice may provide to higher layers the periodic CSI-RS configurationindexes and/or the SS/PBCH block indexes from the second set. Thewireless device may provide, to higher layers, corresponding L1-RSRPmeasurements that may be greater than or equal to the second threshold.

A wireless device may be configured with one CORESET, for example, by ahigher layer parameter (e.g., Beam-failure-Recovery-Response-CORESET).The wireless device may be configured with an associated search spacethat may be provided by a higher layer parameter (e.g.,search-space-config). The associated search space may be used formonitoring a PDCCH in the one control resource set. The wireless devicemay receive from higher layers (e.g., MAC layer), by a parameter (e.g.,Beam-failure-recovery-request-RACH-Resource), a configuration for aPRACH transmission. For the PRACH transmission in slot n and based onantenna port quasi co-location parameters associated with periodicCSI-RS configuration or SS/PBCH block with a first RS index, thewireless device may monitor the PDCCH for detection of a DCI formatstarting from a slot (e.g., slot n+4) within a window. The window may beconfigured by a higher layer parameter (e.g.,Beam-failure-recovery-request-window). The DCI format may be CRCscrambled by a C-RNTI. For a PDSCH reception, the wireless device mayuse the antenna port quasi-collocation parameters (e.g., as formonitoring the PDCCH) until the wireless device receives, by higherlayers, an activation for a TCI state or a parameter (e.g.,TCI-StatesPDCCH).

A base station and/or a wireless device may perform a PRACH-based BFRprocedure. The base station and/or the wireless device may perform aPRACH-based BFR procedure, for example, if at least one beam failureinstance is identified, and/or if a beam correspondence exists betweenthe base station and the wireless device. A wireless device may send(e.g., transmit) an uplink signal, using a transmission beamcorresponding to a receiving beam for receiving a downlink signal fromthe base station, for example, if a beam correspondence exists. Thewireless device may determine RF and/or digital beamforming parametersfor receiving the downlink signal, for example, if the wireless deviceidentifies the receiving beam. The wireless device may determine thetransmission beam by using the RF and/or digital beamforming parameterscorresponding to the receiving beam. Beamforming parameters (e.g., beamweight factors on antenna elements, or other parameters) correspondingto the transmission beam may be same as beamforming parameterscorresponding to the receiving beam. Transceiver design may besimplified, for example, if the base station need not necessarilyindicate the transmission beam used for a downlink transmission or anuplink transmission, which may reduce signaling overhead. A wirelessdevice may, for example, avoid uplink beam sweeping such as to help abase station find a proper uplink beam, which may reduce the powerconsumption of the wireless device. The proper beam may be in thedirection of the wireless device (e.g., from the base station). Beamcorrespondence may exist, for example, in a TDD case, if transmissionand reception share a same set of physical antenna elements, and/or iftransmission and reception have a same or similar beam width.

A beam correspondence may not exist, for example, if a physical antennafor transmission is separated from a physical antenna for reception,and/or if the beam widths corresponding to transmission and receptionare different. A wireless device may not determine a transmission beambased on a receiving beam, for example, if a beam correspondence doesnot exist. A base station may, for example, explicitly indicate atransmission beam for PUCCH and/or PUSCH transmission via an RRCmessage, a MAC CE, and/or DCI. A base station and/or a wireless devicemay not perform a PRACH-based BFR procedure if, for example, at leastone beam failure instance is identified and/or if a beam correspondencedoes not exist.

In some PRACH-based BFR procedures, even if a beam correspondence doesnot exist, a wireless device may still determine a transmission beam forPRACH preamble transmission based on a receiving beam for receiving adownlink signal. The base station may not detect the PRACH preamblebecause the base station, determining that no beam correspondenceexists, may not expect an uplink transmission on the transmission beamused for transmission of the PRACH preamble. The PRACH-based BFRprocedure may result in an unsuccessful beam failure recovery, forexample, if the base station may not detect the PRACH preamble. Anunsuccessful beam failure recovery may lead to a radio link failure.

A wireless device may send (e.g., transmit) a PUCCH signal to a basestation indicating that a BFR procedure is triggered, for example, if atleast one beam failure instance is identified and/or if beamcorrespondence does not exist. A transmission beam for the PUCCH signalmay be indicated by an RRC message, a MAC CE, and/or DCI. HARQ may notbe supported in existing PUCCH transmission. A wireless device may send(e.g., transmit), for example, a CSI report to a base station via aPUCCH resource. The base station may not send (e.g., transmit) aresponse to the wireless device to confirm reception of the CSI report,for example, even if the base station receives the CSI report. Awireless device may send (e.g., transmit), for example, a HARQ-ACKfeedback to a base station via a PUCCH resource. The base station maynot send (e.g., transmit) a response to the wireless device to confirmreception of the HARQ-ACK feedback. For a BFR procedure, a wirelessdevice may expect a response from a base station after the wirelessdevice sends (e.g., transmits) a PUCCH signal to the base station. Thewireless device may determine to repeat transmission of the PUCCHsignal, for example, if no response is received from the base station. Amechanism for a base station's response to a PUCCH signal transmissionmay be used to avoid repeated transmissions. The base station'sconfirmation may ensure that the wireless device and the base stationinteract properly to complete the BFR procedure. An SR-based BFRprocedure, and/or an SR-like BFR procedure, may be enhanced, forexample, if beam correspondence does not exist.

An SR configuration may correspond to at least one logical channel in atleast some SR configurations. An SR configuration may be associated withmultiple parameters corresponding to at least one of: an SR prohibittimer, a maximum number of SR transmissions, a parameter indicating aperiodicity, offset of the SR transmissions, and/or a PUCCH resource.

An SR configuration for a BFR procedure may be different, for example,from an SR configuration associated with at least one logical channel. Awireless device may send (e.g., transmit) a pending SR, for example, upto any first number of times (e.g., up to 64 times or any other value)for the SR configuration associated with the at least one logicalchannel. A wireless device may send (e.g., transmit) an SR, for example,up to any second number of times (e.g., up to 200 times or any othervalue) for the SR configuration for the BFR procedure considering thatbeam correspondence may not exist. The first number of times may be lessthan, equal to, or greater than the second number of times. A responsewindow for a BFR procedure, for example, may be shorter than a responsewindow for an SR for requesting an UL-SCH resource. A response timerassociated with the BFR procedure, for example, may be a first number ofslots (e.g., up to 80 or any other number of slots) subject to a firstconfiguration. An SR prohibit timer for an SR configuration forrequesting an UL-SCH resource, for example, may be a second number ofslots (e.g., up to 128 ms or any other value of time of number of slots)subject to second configuration. An SR configuration for a BFR proceduremay be separately or independently configured from an SR configurationfor requesting an UL-SCH resource. An SR procedure triggered by the BFRprocedure may, for example, be different from an SR procedure forrequesting UL-SCH resource (e.g., BSR triggered).

FIG. 18 shows an example of a PUCCH-based BFR procedure. A base station1802 may transmit at least one message, comprising parameters indicatinga first set of RSs (e.g., RS 0 1804) and a second set of RSs (e.g., RS 11806, RS 2 1808, and RS 3 1810), to a wireless device 1812. The at leastone message may be an RRC message (e.g., an RRC connectionreconfiguration message, an RRC connection reestablishment message,and/or an RRC connection setup message). The first set of RSs mayidentify one or more beams QCLed with a beam on which the base station1802 transmits PDCCH and/or PDSCH signals. The second set of RSs mayidentify one or more candidate beams from which the wireless device 1812may select a candidate beam with quality better than a first threshold,for example, if the one or more beams associated with the first set ofRSs fail. Each RS in the first set and/or second set of RSs may be anSSB, or a CSI-RS. The first threshold may be a configured value based onone or more of a BLER, a SINR, and/or an L1-RSRP. One or more beamsassociated with the first set of RSs may fail, for example, if one ormore measurements on the first set of RSs is worse than a configuredsecond threshold (e.g., RSRP, and/or BLER).

The at least one message transmitted by the base station 1802 maycomprise configuration parameters. The configuration parameters mayindicate, for example, a first request (e.g., a scheduling request, abeam failure request, and/or a beam request) configuration 1814, and/orat least a second SR configuration 1816. The first request configuration1814 may be associated with at least one of: a first PUCCH resource, afirst timer with a first value, a first transmission number, a firstperiodicity for a transmission of the first request, and/or a firstoffset for a transmission of the first request. The at least second SRconfiguration 1816 may be associated with at least one of: a secondPUCCH resource, a second timer with a second value, a secondtransmission number, a second periodicity, and/or a second offset. Theat least second SR configuration may be associated with at least onelogical channel.

The first value for the first timer may be different from the secondvalue of the second timer. The first transmission number may bedifferent from the second transmission number. The first periodicity maybe different from the second periodicity. The first offset may bedifferent from the second offset. The first PUCCH resource may bedifferent from the second PUCCH resource. The wireless device maymaintain a first counter for the first request configuration. Thewireless device may maintain a second counter for each of the at leastsecond SR configuration.

The at least one message may comprise parameters indicating a firstCORESET, and at least a second CORESET. The first CORESET may beassociated with the first request configuration. The second CORESET maybe associated with the second request configuration. The wireless devicemay monitor a first PDCCH on the first CORESET, for example, if thewireless device transmits a first request on the first PUCCH resourcefor a BFR procedure. The wireless device may monitor a second PDCCH onthe at least second CORESET, for example, if the wireless devicetransmits a second SR of the at least second SR configuration.

A base station may send (e.g., transmit), to a wireless device, one ormore messages comprising configuration parameters of one or more cells.The one or more cells may comprise at least one PCell and/or PSCell, andone or more SCells. An SpCell (e.g., PCell or PSCell) and one or moreSCells may operate on different frequencies and/or different bands. AnSCell may support a multi-beam operation. In the multi-beam operation, awireless device may perform one or more beam management procedures(e.g., a beam failure recovery procedure) on the SCell. The wirelessdevice may perform a BFR procedure, for example, if at least one of oneor more beam pair links between the SCell and the wireless device fails.Some BFR procedures may result in inefficiencies if there is a beamfailure for one of the one or more SCells.

A wireless device may receive one or more RRC messages comprisingparameters corresponding to one or more SR configurations. For each ofthe one or more SR configurations, the parameters may indicate at leastone of: an SR prohibit timer, a maximum number of SR transmission, aparameter indicating a periodicity and offset of SR transmission, and/ora PUCCH resource identified by a PUCCH resource index. A wireless devicemay set a SR_COUNTER to a first value (e.g., 0), if: an SR of an SRconfiguration triggered (e.g., is pending), for example, after or inresponse to a BSR being triggered on an LCH corresponding to the SRconfiguration; and/or if there are no other pending SRs corresponding tothe SR configuration.

A wireless device may determine whether there is at least one validPUCCH resource for a pending SR at the time of an SR transmissionoccasion. The wireless device may initiate a random access procedure ona PCell, for example, if there is no valid PUCCH resource for thepending SR. The wireless device may cancel the pending SR, for example,if there is no valid PUCCH resource for the pending SR.

A wireless device may determine an SR transmission occasion on the atleast one valid PUCCH resource, for example, if there is at least onevalid PUCCH resource for a pending SR. The wireless device may determinethe SR transmission occasion based on a periodicity and an offset of SRtransmission, for example, as may be indicated in one or more RRCmessages. The wireless device may wait for another SR transmissionoccasion, for example, if an SR prohibit timer is running. The wirelessdevice may increment an SR_COUNTER (e.g., by one) and/or instruct aphysical layer of the wireless device to signal the SR on the at leastone valid PUCCH resource for the SR if: (i) the SR prohibit timer is notrunning, (ii) the at least one valid PUCCH resource for the SRtransmission occasion does not overlap with a measurement gap, (iii) theat least one valid PUCCH resource for the SR transmission occasion doesnot overlap with an uplink shared channel (UL-SCH) resource, and/or (iv)the SR_COUNTER is less than the maximum number of SR transmission. Thephysical layer of the wireless device may transmit a PUCCH on the atleast one valid PUCCH resource for the SR. The wireless device maymonitor a PDCCH for detecting DCI for an uplink grant, for example,after or in response to transmitting the PUCCH. The wireless device maycancel the pending SR, and/or the wireless device may stop the SRprohibit timer, for example, if the wireless device receives one or moreuplink grants that may accommodate all pending data available fortransmission. The wireless device may cancel the pending SR, and/or thewireless device may stop the SR prohibit timer, for example, any timeduring the above SR procedure. A wireless device may repeat one or moreactions (e.g., if the wireless device does not receive one or moreuplink grants which may accommodate all pending data available fortransmission) comprising: determining the at least one valid PUCCHresource; determining whether the SR prohibit timer is running;determining whether the SR_COUNTER is less than, equal to, or greaterthan a maximum number of SR transmission; incrementing the SR_COUNTER;transmitting the SR and/or starting the SR prohibit timer; and/ormonitoring a PDCCH for uplink grant. A wireless device may release aPUCCH for one or more serving cells, release an SRS for the one or moreserving cells, clear one or more configured downlink assignments anduplink grants, initiate a random access procedure on a PCell, and/orcancel the pending SR, for example, if the SR_COUNTER indicates a numberequal to or greater than a maximum number of SR transmissions.

A wireless device may operate, for example, on or using multiple activeBWPs simultaneously. A wireless device may perform one or more beammanagement procedures described herein (e.g., a BFR procedure) on orusing one of the multiple active BWPs. The wireless device may perform aBFR procedure, for example, if at least one of one or more beam pairlinks of the wireless device on the one of the multiple active BWPsfails.

Some or all of the beam procedures described herein (e.g., BFRprocedures) may be enhanced, for example, to improve downlink radioefficiency and/or reduce uplink signaling overhead if carrieraggregation (CA) is configured for a wireless device Some or all of thebeam procedures described herein (e.g., BFR procedures) may be enhancedto improve downlink radio efficiency and/or reduce uplink signalingoverhead if multiple active BWPs are configured for a cell.

A wireless device may determine and/or use at least one valid PUCCHresource for a pending SR of the wireless device. The wireless devicemay not transmit the pending SR, for example, if the at least one validPUCCH resource for the pending SR overlaps with an UL-SCH resourcecorresponding to a TB. The wireless device may transmit the TB via theUL-SCH resource. The wireless device may delay the transmission of thepending SR, for example, until at least one valid PUCCH resource for thepending SR does not overlap with an UL-SCH resource.

A wireless device may delay a transmission of a triggered request (e.g.,a scheduling request, a beam failure request, a beam request, a beamfailure recovery request, PUCCH-based BFR, and/or the like, etc.) for aPUCCH-based BFR procedure, for example, until at least one valid PUCCHresource for the triggered request does not overlap with an UL-SCHresource. A beam failure recovery timer configured by an RRC message mayexpire and/or the PUCCH-based BFR procedure may not be successful.Unsuccessful BFR procedure(s) may result in inefficiencies and higherincidences of radio link failure(s) (RLF).

At least one valid PUCCH resource for a transmission occasion of atriggered request for a BFR procedure may overlap with an UL-SCHresource for transmission of at least TB. A base station may transmitone or more acknowledgement (ACK) signals associated with the uplinksignal, for example, if the wireless device drops the triggered requestand transmits an uplink signal scheduled on the UL-SCH resource. Thewireless device may monitor at least one PDCCH in one or more CORESETsfor the one or more ACK signals. The at least one PDCCH may fail (e.g.,due to a radio link quality less than a threshold) during the BFRprocedure. The wireless device may not receive the one or more ACKsignals. The wireless device may retransmit the uplink signal, forexample, if the wireless device does not receive the one or more ACKsignals. Dropped requests, additional monitoring, failed transmissions,and/or retransmissions may result in signaling overhead, transmissionlatency, and wasted resources. Transmitting an uplink signal via UL-SCHduring a BFR procedure, for example, may increase the transmissionlatency.

PUCCH-based BFR procedures may be enhanced to improve downlink radioefficiency, reduce uplink signaling overhead, and/or reduce a durationof a BFR procedure. A wireless device may, for example in legacysystems, drop an SR transmission and/or perform an UL-SCH transmission,if an SR is triggered and a valid PUCCH resource for the triggered SRoverlaps with an UL-SCH resource. An SR-based BFR procedure may be usedfor a cell (e.g., primary cell (PCell), secondary cell (SCell), etc.).The wireless device may transmit a request (e.g., SR-like, PRACH-based,etc.) via a PUCCH resource for the BFR procedure of an SCell, forexample, if the wireless device initiates a beam failure recovery (BFR)procedure for the SCell.

A wireless device may drop a request for a BFR procedure (e.g., thewireless device may not transmit a BFR signal) of the SCell if a PUCCHresource to be used for transmission of the request overlaps with anUL-SCH resource. Dropping the request for the BFR procedure may increasedelay for the BFR procedure. Even if the UL-SCH transmission isperformed after dropping the request, the wireless device may notreceive an ACK/NACK, for the UL-SCH transmission, in the downlinkcontrol channels of the SCell (e.g., if the downlink control channels ofthe SCell has a beam failure). Dropping the request for the BFRprocedure and/or failure to receive an ACK/NACK may lead toretransmission of the UL-SCH transmission, which may result in increaseduplink interference to other cells and/or other wireless devices,increased resource/signaling overhead, and/or increased latency.

The wireless device may drop an UL-SCH transmission and perform thetransmission of a request for a BFR procedure (e.g., SR-like,PRACH-based), even if the the request overlaps with an UL-SCH resource.The request for a BFR procedure may, for example, be set to have ahigher priority than UL-SCH transmission. By transmitting the requestfor a BFR procedure and dropping an UL-SCH transmission, the wirelessdevice may reduce uplink interference to other cells and/or to otherwireless device, decrease resource signaling overhead, and or decreaselatency.

A wireless device may not be capable of transmitting and/or receivingwith two different beams at the same time (e.g., such as a legacy deviceand/or a device that supports 3GPP Release 15 or earlier). The wirelessdevice may not be able to receive a downlink control channel (e.g.,PDCCH) with a first beam and a downlink shared channel (e.g., PDSCH)with a second beam, for example, if the first beam and the second beamare different and/or are not QCL-ed. Each CORESET except a dedicatedbeam failure recovery (BFR) coreset may be configured with a referencesignal (RS) associated with a beam. A base station may configure a firstCORESET with a first RS associated with a first beam and a secondCORESET with a second RS associated with a second beam. The wirelessdevice may monitor for and receive DCI in the first CORESET with thefirst beam and monitor for and receive DCI in the second CORESET withthe second beam. The wireless device may receive the DCI with a higherror rate, for example, if the wireless device attempts to receive DCIin the first CORESET with a second beam. The wireless device may not beable to decode the DCI, for example, if a high error rate occurs, whichmay result in a long delay for a transmission.

A wireless device may monitor and receive a DCI (e.g., beam failurerecovery response) via a dedicated BFR CORESET with a candidate beamselected for a BFR procedure. The beam that the wireless device monitorsand receives DCI in the dedicated BFR CORESET may change depending onthe selected candidate beam. A dedicated BFR coreset that may bedifferent from the other CORESETS may not be preconfigured with a fixedbeam. The wireless device and the base station may not know whichcandidate beam the wireless device will chose, for example, if thewireless device initiates a BFR procedure.

The wireless device may detect a beam failure, for example, if thewireless device is monitoring the first CORESET and the second CORESET.The wireless device may monitor both a dedicated BFR CORESET for a BFRresponse and other (e.g., old) CORESETS (e.g., the first CORESET and thesecond CORESET), for example, if the wireless device initiates a BFRprocedure based on the detecting the beam failure. The wireless devicemay not monitor the dedicated BFR CORESET, for example, before the BFRprocedure is initiated.

The wireless device may transmit an uplink signal (e.g., a preamble) fora BFR procedure. The uplink signal may be associated with a selectedcandidate beam. The wireless device may start monitoring the dedicatedBFR CORESET with the candidate beam, for example, based on or inresponse to transmitting the uplink signal. The wireless device maymonitor the first CORESET with the first beam and the second CORESETwith the second beam, for example, during the BFR procedure.

Problems may occur, for example, if the dedicated BFR CORESET overlaps,in time, with the first CORESET and/or the second CORESET. If thecandidate beam is different from the first beam and/or the second beam,the wireless device may not receive DCI in the dedicated BFR CORESET andthe first CORESET and/or the second CORESET. The wireless device mayapply only one beam at a time (e.g., such as a legacy device and/or adevice that supports 3GPP Release 15). The base station may havedifficulty determining a behavior of the wireless device, which mayresult in a lack of synchronization between the base station and thewireless device.

Higher priority may be applied to the dedicated BFR CORESET, forexample, which may address the above problem(s). The wireless device maynot receive a BFR response, for example, if the wireless device monitorsthe dedicated BFR CORESET for a BFR response with the first beam of thefirst CORESET or the second beam of the second CORESET. The wirelessdevice may have already detected a beam failure based on the quality ofthe first beam and the second beam, which may have been a reason why thewireless device initiated the BFR procedure. Relying on beams (e.g., thefirst beam and the second beam) that have a beam failure may result indecoding errors. The wireless device may not receive the BFR response,for example, if the first beam and/or the second beam is used to receivethe BFR response. Such failure to receive the BFR response may increasethe duration of the BFR procedure, which may increase the latency ofconnection reestablishment between the base station and the wirelessdevice. The wireless device may determine a radio link failure, forexample, if the latency increases (e.g., above a threshhold). Radio linkfailure may cause communications between a base station and a wirelessdevice to start/re-start from beginning (e.g., initial random-access,etc) to establish communications that may take longer (e.g., muchlonger) than a BFR procedure.

A wireless device may monitor both a dedicated BFR CORESET and anoverlapped CORESET (e.g., the first CORESET and/or the second CORESET)with the candidate beam. Such monitoring may help to ensure that thewireless device does not miss a BFR response in the dedicated BFRCORESET, while still allowing the wireless device an opportunity todetect DCI in the overlapped coreset. The wireless device may not beable to receive the DCI in the overlapped CORESET, but the wirelessdevice may still be able to attempt to decode DCI in the overlappedCORESET.

A wireless device may monitor only a dedicated BFR CORESET with thecandidate beam, and stop monitoring the overlapped CORESET (e.g., thefirst CORESET and/or the second CORESET). By monitoring only thededicated BFR CORESET, the wireless device may be able to avoid missingthe BFR response in the dedicated BFR CORESET. By not monitoring theoverlapped CORESET, the wireless device may not consume power with themonitoring. Such monitoring of only a dedicated BFR CORESET may conservebattery power for the wireless device.

One or more component carriers (e.g., intra-band cells) may be poweredby a single RF chain (e.g., such as a legacy device and/or a device thatsupports 3GPP Release 15). The wireless device may apply a single TX/RXspatial filter (e.g., beam) at a time for the one or more componentcarriers. The wireless device may not receive/transmit the firstchannel/RS and the second channel/RS simultaneously, for example, if afirst channel/RS with a first QCL assumption overlaps with a secondchannel/RS with a second QCL assumption different from the first QCLassumption.

A wireless device may drop a first channel/RS with a first QCLassumption, for example, if the first channel/RS overlaps with a secondchannel/RS, for a BFR procedure, with a second QCL assumption differentfrom the first QCL assumption. A wireless device may override a firstchannel/RS with a first QCL assumption, for example, if the firstchannel/RS overlaps with a second channel/RS, for a BFR procedure, witha second QCL assumption different from the first QCL assumption.Dropping and/or overriding the first channel/RS in favor of the secondchannel/RS may ensure that the BFR procedure is not delayed.

FIG. 19 shows an example BFR procedure by a wireless device. At t₁, awireless device may detect at least one beam failure according to atleast one BFR parameter and initiate a BFR procedure. The wirelessdevice may select a beam based on detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., based on RSRP, SINR, and/or BLER above a threshold value) thatmay be selected from a set of candidate beams. At t₂, the wirelessdevice may send (e.g., transmit) at least a BFR signal 1904 to a basestation, for example, based on selecting the beam (e.g., selected beam).The BFR signal 1904 may be associated with the selected beam. The BFRsignal 1904 may be transmitted on a PUCCH resource 1908. The PUCCHresource 1908 may overlap, for example, with an UL-SCH resource. ThePUCCH resource 1908 may overlap, for example, with a PUSCH resource 1912for transmission of a data 1916. The wireless device may droptransmission of the data 1916 scheduled on the PUSCH resource 1912, forexample, if the PUCCH resource 1908 of the BFR signal 1904 overlaps withthe PUSCH resource 1912 of the data 1916.

FIG. 20 shows an example BFR procedure at a wireless device. At step2000, a wireless device may receive one or more RRC messages comprisingBFR parameters. The one or more RRC messages may comprise, for example,an RRC message (e.g., RRC connection reconfiguration message, RRCconnection reestablishment message, and/or RRC connection setupmessage). At step 2004, the wireless device may trigger a BFR procedure.The wireless device may trigger a first request for the BFR procedure.The first request may be associated with a first request configuration.The wireless device may initiate the BFR procedure, for example, if thewireless device detects a beam failure. The wireless device may set afirst counter to a first value (e.g., 0). The first counter may be, forexample, an SR_COUNTER.

At step 2008, the wireless device may determine whether it has a validPUCCH resource for the first request. At step 2016, the wireless devicemay cancel the BFR procedure and the wireless device may initiate arandom access (RA) procedure. The wireless device may cancel the firstrequest associated with the first request configuration. The wirelessdevice may keep pending a second request (e.g., an SR), that may beassociated with the at least a second request configuration, for the BFRprocedure, for example, if the first PUCCH resource has been released.The wireless device may initiate a RA procedure for a BFR, or an initialRA procedure, for example, if the wireless device determines no validPUCCH resource for the first request configuration according toconfiguration parameters of the first resource configuration. Thewireless device may determine no valid PUCCH resource for the firstresource configuration, for example, if a PUCCH resource has beenreleased.

At step 2012, the wireless device may determine if the valid PUCCHresource overlaps with a

UL-SCH resource. At step 2020, the wireless may drop an uplinktransmission scheduled on the UL-SCH if the wireless device determinesthat the valid PUCCH resource overlaps with the UL-SCH resource.

At step 2024, the wireless device may determine if a value of the firstcounter is less than a value corresponding to a first transmissionnumber. The first transmission number may be a configured maximum numberof SR transmissions (e.g., sr_TransMax for BFR). The first transmissionnumber may be configured by one or more RRC messages. A lower layer(e.g., MAC layer or PHY layer) of the wireless device may indicate afailure of the BFR procedure to a higher layer (e.g., RRC layer) of thewireless device. The wireless device may initiate, for example, an RAprocedure for a BFR. The wireless device may, for example, cancel thefirst request associated with the first request configuration. Thewireless device may, for example, keep pending a second requestassociated with at least a second request configuration.

At step 2028, the wireless device may transit a first BFR signalcorresponding to a first request. The wireless device may transmit thefirst BFR signal, for example, if the valid PUCCH resource does notoverlap with a measurement gap. The wireless device may transmit a PUCCHsignal on the valid PUCCH resource if transmitting the first BFR signal.The PUCCH signal may comprise, for example, at least one parameterindicating one of: a RS index indicating the candidate beam, and/or ameasurement quality (e.g., an RSRP) of a candidate beam. The first BFRsignal may be configured with multiple PUCCH resources in at least onemessage. Each PUCCH resource may be associated with one of a set of RSs(e.g., the second set of RSs as described above with reference to FIG.18). A wireless device may, for example, select a candidate beam fromthe second set of RSs. The wireless device may determine the valid PUCCHresource from the multiple PUCCH resources associated with the candidatebeam. The wireless device may transmit the PUCCH signal on the validPUCCH resource. The PUCCH signal may, for example, be a single bit orany number of bits. The bit(s) may be set, for example, to a first value(e.g., one), indicating: a BFR procedure is triggered and/or a candidatebeam associated with the PUCCH resource is identified.

Further at step 2028, the wireless device may start a first timer, forexample, based on transmitting the first BFR signal. The first timer maybe, for example, a beam failure recovery timer. The wireless device mayincrement the first counter (e.g., by one), for example, based ontransmitting transmitting the first BFR signal. The wireless device may,for example, increment the first counter by one for every transmissionof a BFR signal (e.g., the first BFR signal, a subsequent second BFRsignal, etc.). At step 2044, the wireless device may determine that theBFR procedure is unsuccessful, for example, if the wireless devicedetermines that a value of the first counter is greater than or equal tothe value corresponding to the first transmission number. The wirelessdevice may not drop an uplink transmission scheduled on the UL-SCHresource, for example, if the first counter indicates a value greaterthan or equal to the first transmission number. The wireless device may,for example, perform the uplink transmission scheduled on the UL-SCHresource.

At step 2032, the wireless device may monitor a PDCCH. The wirelessdevice may monitor a PDCCH on a dedicated CORESET, for example, whilethe first timer is running. The wireless device may monitor the PDCCH todetect, for example, DCI. At step 2036, the wireless device maydetermine if the wireless device has received DCI while the first timerwas running. At step 2040, the wireless device may cancel the BFRprocedure if the wireless device determines that the wireless device hasreceived the DCI while the first timer was running, wherein the wirelessdevice may determine that the BFR procedure has completed successfully.The wireless device may stop the first timer, and/or the wireless devicemay reset the first counter, based on or in response to completing theBFR procedure successfully. The wireless device may cancel the firstrequest associated with the first request configuration. The wirelessdevice may cancel a pending second request associated with at least asecond request configuration. The one or more uplink grants mayaccommodate pending data available for transmission. The wireless devicemay cancel the first request associated with the first requestconfiguration and keep pending a second request (e.g., an SR) associatedwith the at least a second request configuration, for example, if DCIreceived on the PDCCH comprises one or more downlink assignments. Thewireless device may avoid a RLF, for example, if the BFR procedurecompletes successfully while the first timer is running. The BFRprocedure may return to step 2008, for example, if the wireless devicedetermines that the first timer has expired prior to receiving DCI.

A valid PUCCH resource for a BFR procedure may overlap with, forexample, an UL-SCH resource for transmission of a TB. The wirelessdevice may drop an uplink transmission scheduled on an UL-SCH resource,for example, if a valid PUCCH resource for a BFR procedure overlaps withan UL-SCH resource. An ongoing BFR procedure may have a higher prioritythan, for example, an uplink transmission scheduled on an UL-SCHresource. Dropping a scheduled transmission via an UL-SCH may reduce anuplink interference to other wireless devices and/or in other cells.During a BFR procedure of a serving cell, inter symbol interference toother wireless devices may occur, for example, if the serving cell isused as a timing reference cell. During a BFR procedure of a servingcell, a wireless device may have an incorrect pathloss estimation, forexample, if the serving cell is used as a pathloss reference cell.Incorrect pathloss estimation may result in interference to otherwireless devices and/or other cells.

FIG. 21A shows an example of a BFR procedure. A wireless device mayreceive, from a base station, an uplink grant with a first number ofrepetitions (e.g., 7, 8, or any other number). The base station mayschedule the wireless device on an UL-SCH resource for an uplinktransmission 2102. The wireless device may perform the uplinktransmission 2102, for example, using the UL-SCH resource with the firstnumber of repetitions. The wireless device may trigger a BFR procedureat time ti, for example, if the wireless device detects a beam failure.The wireless device may suspend a transmission of a BFR signal until theuplink transmission 2102 is completed, for example, if a request for aPUCCH-based BFR procedure is triggered and a valid PUCCH resource forthe BFR procedure overlaps with the UL-SCH resource. The wireless devicemay transmit, for example, a BFR signal 2104 on the valid PUCCH resourceafter the uplink transmission 2102 on the resources indicated by theuplink frant with the first number of repetitions. Suspending thetransmission of the BFR signal until the uplink transmission 2102 iscompleted may result in a delay of the PUCCH-based BFR procedure. Adelay of the PUCCH-based BFR procedure may result in an RLF.

FIG. 21B shows another example of a BFR procedure. A wireless device mayreceive, from a base station, an uplink grant with a first number ofrepetitions (e.g., 7, 8, or any other number). The base station mayschedule the wireless device on an UL-SCH resource for an uplinktransmission 2112. The wireless device may perform the uplinktransmission 2112-1, for example, over the UL-SCH resource. The wirelessdevice may trigger a request for a BFR procedure at time ti, during anuplink transmission 2112-1, for example, if the wireless device detectsa beam failure. The wireless device may drop the uplink transmissionscheduled on the UL-SCH resource if the BFR procedure is triggered and avalid PUCCH resource for the BFR procedure overlaps with the UL-SCHresource. The wireless device may, for example, transmit a first BFRsignal 2116 on the valid PUCCH resource and drop at least a portion ofthe uplink transmission 2112 if the BFR procedure is triggered. Thewireless device may, for example, resume the uplink transmission 2112,for example, after the first BFR signal 2116 is transmitted, bytransmitting an uplink transmission 2112-2. The uplink transmission2112-2 may be performed during the PUCCH-based BFR procedure, forexample, if the valid PUCCH resource does not overlap with the UL-SCHresource. The wireless device may transmit, for example, a second BFRsignal 2120 on the valid PUCCH resource and drop at least a portion ofthe uplink transmission 2112 if the BFR procedure is triggered. Theuplink transmission scheduled on the UL-SCH resource may be delayedand/or suspended, for example, at least until the PUCCH-based BFRprocedure is completed. The wireless device may resume an uplinktransmission 2112-3 scheduled on the UL-SCH resource based on or inresponse to the PUCCH-based BFR procedure being completed. Dropping theuplink transmission scheduled on the UL-SCH resource may, for example,enable the PUCCH-based BFR procedure to be completed in a timely mannerand/or with reduced delay.

A wireless device may report, to a base station via a capabilitysignaling procedures of the wireless device, an RF capability of thewireless device corresponding to reception and/or transmission ofsignals. The base station may determine whether the wireless device maysimultaneously receive/transmit physical channels and/or RSs viadifferent receiving/transmitting beams from one or more componentcarriers in the downlink/uplink, for example, based on the capabilitysignaling procedures of the wireless device.

A base station may configure one or more component carriers in the sameband to a wireless device, for example, using intra-band CA. The one ormore component carriers may be powered by a same and a single RF chain.The wireless device may apply a single and/or a same set of TX/RXspatial parameters to the one or more component carriers in the sameband at the same time instant. Applying the single and/or the same setof TX/RX spatial parameters may impose limitations on flexibility ofmultiplexing physical channels (e.g., PDSCH/PUSCH, PDCCH/PUCCH, SRS,PRACH, etc.) and/or RSs (e.g., CSI-RS, SSB, etc.), such as both withinand across the one or more component carriers.

A first channel/RS and a second channel/RS may be multiplexed in thesame OFDM symbols, for example, if the first channel/RS of a firstserving cell (e.g., PCell, BWP) is associated (e.g., QCL-TypeD′) withthe second channel/RS of a second serving cell (e.g., SCell, BWP). Awireless device may transmit (or receive) the multiplexed firstchannel/RS and the second channel/RS simultaneously in uplink (ordownlink).

One or more first antenna ports of a first serving cell and one or moresecond antenna ports of a second serving cell, for example, may not beassociated (e.g., QCL-TypeD′). A wireless device may not, for example,infer one or more channel properties of the one or more first antennaports of the first serving cell from the one or more second antennaports of the second serving cell.

A first channel/RS (e.g., PDSCH/PUSCH, PDCCH/PUCCH, SRS, PRACH, CSI-RS,SSB, etc.) and a second channel/RS (e.g., PDSCH/PUSCH, PDCCH/PUCCH, SRS,PRACH, CSI-RS, SSB, etc.), for example, may not be associated (e.g.,QCL-TypeD′). A base station may configure the first channel/RS with afirst QCL assumption. The base station may configure the secondchannel/RS with a second QCL assumption. A first transmission/receptionof a first channel/RS and a second transmission/reception of the secondchannel/RS, for example, may overlap (e.g., in at least one OFDMsymbol). A wireless device may transmit/receive a channel/RS with ahigher priority, for example, if the first QCL assumption and the secondQCL assumption are not the same. The wireless device may, for example,drop and/or skip a channel with a lower priority. A first channel/RSmay, for example, be deemed more important than a second channel/RS. Thefirst channel/RS (e.g., associated with a BFR procedure), for example,may have a higher priority than the second channel/RS. The wirelessdevice may perform the first transmission/reception of the firstchannel/RS, via the first QCL assumption associated with the BFRprocedure. The wireless device may perform the secondtransmission/reception of the second channel/RS with the second QCLassumption, for example, after the first transmission/reception of thefirst channel/RS (e.g., sequentially based on the priority).

A first transmission/reception of a first channel/RS and a secondtransmission/reception of a second channel/RS may overlap (e.g., in atleast one OFDM symbol). The wireless device may override the first QCLassumption (or the second QCL assumption), for example, if the first QCLassumption of the first channel/RS and the second QCL assumption of thesecond channel/RS are not the same. The wireless device may perform thefirst transmission/reception of the first channel/RS with the second QCLassumption, for example, if the wireless device overrides the first QCLassumption. The wireless device may perform the first transmission andthe second transmission simultaneously with the second QCL assumption.The performing the first transmission/reception of the first channel/RSwith the second QCL assumption may result in missing and/or poorlyreceiving the first channel/RS.

A first transmission of a first channel/RS of a first serving cell and asecond transmission of a second channel/RS of a second serving cell mayoverlap (e.g., in at least one OFDM symbol). A base station mayconfigure the first channel/RS with a first QCL assumption. The basestation may configure the second channel/RS with a second QCLassumption. The wireless device may simultaneously transmit the firstchannel/RS and the second channel/RS, for example, if the first QCLassumption and the second QCL assumption are the same. For simultaneoustransmission of the first channel/RS of the first serving cell and thesecond channel/RS of the second serving cell, a prioritization rule maybe applied, for example, if the first QCL assumption and the second QCLassumption are not the same. The prioritization rule may be based on atleast one of content and/or importance of the first channel/RS and thesecond channel/RS. The first serving cell may, for example, have anongoing BFR procedure. The first channel/RS (e.g., PRACH, PUCCH, SSB)may, for example, be used for a BFR procedure (e.g., preambletransmission via PRACH). A BFR procedure (e.g., via PRACH, PUCCH, etc.)may have a higher priority than, for example, data transmission on aPUSCH. The wireless device may perform a first transmission and drop asecond transmission (e.g., in a slot, mini-slot, etc.), for example, ifa first serving cell has an ongoing BFR procedure. The first servingcell and the second serving cells may be BWPs on a same carrier (e.g.,multiple active BWPs). The first serving cell and the second servingcell may be intra-band carrier-aggregation component carriers (e.g., thefirst serving cell may be a PCell and the second serving cell may be anSCell).

A first transmission of a first channel/RS of a first serving cell and asecond transmission of a second channel/RS of a second serving cell mayoverlap (e.g., in at least one OFDM symbol). A base station mayconfigure the first channel/RS with a first QCL assumption. The basestation may configure the second channel/RS with a second QCLassumption. The wireless device may simultaneously transmit the firstchannel/RS and the second channel/RS, for example, if the first QCLassumption and the second QCL assumption are the same. For simultaneoustransmission of the first channel/RS of the first serving cell and thesecond channel/RS of the second serving cell, an overriding rule may beapplied, for example, if the first QCL assumption and the second QCLassumption are not the same. The overriding rule may be based on atleast one of content and/or importance of the first channel/RS and thesecond channel/RS. The first serving cell may, for example, have anongoing BFR procedure. The first channel/RS (e.g., PRACH, PUCCH, SSB)may, for example, be used for a BFR procedure (e.g., preambletransmission via PRACH). A BFR procedure (e.g., via PRACH, PUCCH, etc)may have a higher priority than, for example, data transmission on aPUSCH. The wireless device may apply a first QCL assumption of the firstchannel/RS of the first serving cell to both the first transmission ofthe first serving cell and the second transmission of the second servingcell. The first and the second serving cells may, for example, be BWPson a same carrier (e.g., multiple active BWPs). The first and the secondserving cells may, for example, be intra-band carrier-aggregationcomponent carriers (e.g., the first serving cell may be a PCell and thesecond serving cell may be an SCell). The base station may miss areception of the first transmission, for example, if the wireless devicedoes not apply the first QCL assumption of the first channel/RS to thefirst transmission for the ongoing BFR procedure. Missing the receptionof the first transmission may increase latency of the ongoing BFRprocedure. Missing the reception of the first transmission may lead toan RLF.

A wireless device and/or a base station may enhance a BFR procedure, forexample, in a carrier aggregation scenario and/or if bandwidth parts areconfigured for a cell, by performing processed described herein. Aduration of a BFR procedure may be reduced and/or battery powerconsumption may be reduced. BFR procedures may be enhanced to improvedownlink radio efficiency and/or reduce uplink signaling overhead, forexample, if there is a beam failure in a carrier aggregation scenarioand/or if bandwidth parts are configured for a cell.

FIG. 22A and FIG. 22B show examples for BFR procedures. A base stationmay configure a first channel/RS of a Cell 1 with a first QCL assumptionand a second channel/RS of a Cell 2 with a second QCL assumption. Afirst transmission of the first channel/RS and a second transmission ofthe second channel/RS may overlap (e.g., in at least one OFDM symbol attime T1). A wireless device and/or a base station may determine that thefirst channel/RS may be more important than the second channel/RS. Thefirst channel/RS may, for example, have a higher priority than thesecond channel/RS.

In FIG. 22A, if a first QCL assumption of the Cell 1 and a second QCLassumption of the Cell 2 are not the same, the wireless device may, forexample, override the second QCL assumption of the Cell 2. At time Ti,the wireless device may, for example, apply the first QCL assumption ofa first channel/RS of the Cell 1 to both a first transmission of theCell 1 (e.g., transmission 2204) and a second transmission of the Cell 2at time T1 (e.g., transmission 2208). The wireless device may override afirst QCL assumption of the first channel/RS, for example, if the firstchannel/RS and the candidate RS are not associated (e.g., QCL TypeD′).The wireless device may apply a second QCL assumption of the candidateRS of the Cell 2 to both the first transmission of the Cell 1 (e.g.,transmission 2212) and the at least one preamble transmission of theCell 2 at time T3 (e.g, transmission 2216).

In FIG. 22B, if a first QCL assumption of the Cell 1 and the second QCLassumption of the Cell 2 are not the same, the wireless device may, forexample, drop the second transmission of the Cell 2. At time Ti, thewireless device may, for example, perform a first transmission of afirst channel/RS in Cell 1 (e.g., transmission 2224) with the first QCLassumption and drop (or skip) a second transmission of the Cell 2 attime T1. The wireless device may drop the first transmission of thefirst channel/RS, for example, if the first channel/RS and the secondchannel/RS are not associated (e.g., QCL Type D′). The wireless devicemay perform the at least one preamble transmission of the Cell 2 with asecond QCL assumption of the candidate RS (e.g., transmission 2228) anddrop the first transmission of the Cell 1 at time T3.

A wireless device may declare a beam failure of Cell 2, for example, attime T2. The wireless device may initiate an RA procedure for a BFRprocedure. The wireless device may initiate a candidate beamidentification procedure based on initiating the RA procedure for theBFR procedure. The wireless device may indicate a candidate RS in one ormore RSs (e.g., a periodic CSI-RS, an SSB, etc.) of the Cell 2 for thecandidate beam identification procedure. The one or more RSs may beprovided by RRC signaling. A radio link quality (e.g., a BLER, anL1-RSRP) of the candidate RS may be better (e.g., a lower BLER, a higherL1-RSRP, and/or a higher SINR) than a threshold. The threshold may be avalue provided by, for example, a higher layer (e.g. RRC, MAC). Thecandidate RS may be associated with a BFR procedure resource of one ormore BFR procedure resources of the Cell 2. The one or more BFRprocedure resources may be provided, for example, by a base station viaRRC signaling. The BFR procedure resource may comprise, for example, atleast one preamble and at least one PRACH (e.g., time and/or frequency)resource. The BFRQ resource may comprise, for example, a PUCCH resourcefor a PUCCH-based BFR.

A first transmission of a first channel/RS of the Cell 1 and the atleast one preamble transmission of the Cell 2 via the at least one PRACHresource associated with the candidate RS may overlap (e.g., in at leastone OFDM symbol at time T3). The base station may not receive the atleast one preamble, for example, if the wireless device does nottransmit the at least one preamble via the at least one PRACH resourcewith a QCL assumption of the candidate RS. The wireless device may notcomplete the BFR procedure successfully, for example, if the basestation does not receive the at least one preamble. This may result inan increase in a latency of the BFR procedure and/or result in adeclaration of RLF by the wireless device. Cell 1 and Cell 2 may be, forexample, a PCell and an SCell, respectively. Cell 1 and Cell 2 may be,for example, an SCell and a PCell, respectively. Cell 1 and Cell 2 maybe, for example, a first active BWP and a second active BWP of the samecarrier, respectively.

The base station may transmit a BFR response in one or more CORESETS,for example, based on receiving the at least one preamble via the atleast one PRACH resource. The one or more CORESETS may be configured bya base station, for example, via RRC signaling. The wireless device maymonitor at least one PDCCH in one or more CORESETs for the BFR responseto complete the BFR procedure. The one or more CORESETs may be, forexample, on the Cell 1 or the Cell 2. The wireless device may monitorthe at least one PDCCH in the one or more first CORESETs according to anantenna port associated (e.g., QCLed) with the candidate RS. At leastone RS (e.g., DM-RS) of the at least one PDCCH may be associated (e.g.,QCLed) with the candidate RS. A base station may transmit an indicationof QCL between antenna port(s) of the candidate RS and the at least oneRS.

The base station may drop a first transmission of a first channel/RS ofthe Cell 1, for example, if the first transmission of the Cell 1 and asecond transmission of a BFR response associated with a candidate RS ofthe Cell 2 overlap (e.g., in at least one OFDM symbol). The base stationmay transmit the second transmission of the BFR response in one or morefirst CORESETs according to an antenna port associated (e.g., QCLed)with the candidate RS. The wireless device may receive at least onePDCCH in the one or more first CORESETs according to an antenna portassociated (e.g., QCLed) with the candidate RS.

The base station may transmit a first transmission of a first channel/RSof the Cell 1 simultaneously with a second transmission of the BFRresponse associated with a candidate RS of the Cell 2, for example, ifthe first transmission and the second transmission overlap (e.g., in atleast one OFDM symbol). The first transmission and the secondtransmission are transmitted simultaneously, for example, according toan antenna port associated (e.g., QCLed) with the candidate RS. Thewireless device may receive at least one PDCCH in one or more firstCORESETs according to the antenna port associated (e.g., QCLed) with thecandidate RS.

A wireless device may allocate power to PUSCH, PUCCH, PRACH, and/or SRStransmissions based on a priority order, such as for a single celloperation with two uplink carriers or for an operation with carrieraggregation, for example, if a total wireless device transmit power forthe PUSCH, the PUCCH, the PRACH, and/or the SRS transmissions in a firsttransmission period exceeds a maximum transmit power (e.g., which may beconfigured by a higher layer, RRC, MAC, etc.). The priority order maybe, for example, pre-defined or fixed. Allocating power based on apriority order may enable the wireless device not to exceed the maximumtransmit power in the first transmission period. The first transmissionperiod may comprise of one or more symbols. A BFR procedure for an SCellmay have a higher priority than an uplink transmission (e.g., PUSCH,PUCCH, etc) of a PCell. The priority order (e.g., in descending order)may be, for example: a PRACH transmission on a PCell, a PRACHtransmission on a serving cell other than the PCell for a BFR procedure,PUCCH transmission with HARQ-ACK/SR or a PUSCH transmission withHARQ-ACK, a PUCCH transmission with CSI or a PUSCH transmission withCSI, a PUSCH transmission without HARQ-ACK or CSI, and a SRStransmissions (with aperiodic SRS transmissions having higher prioritythan semi-persistent and/or periodic SRS transmissions), or a PRACHtransmission on a serving cell other than the PCell. A PRACHtransmission for a BFR procedure may have a higher priority than otheruplink transmissions (e.g., a PUSCH transmission, or a PUCCHtransmission). By prioritizing transmissions such as described above, aBFR procedure may be completed successfully in a timely manner and/orwith reduced delay.

A wireless device may receive, from a base station, one or more messagescomprising one or more configuration parameters. The one or moreconfiguration parameters may indicate one or more PUCCH resources fortransmission of a first signal for a BFR procedure of a cell. The one ormore configuration parameters may indicate, for example, one or morefirst RSs of the cell, one or more second RSs of the cell, and/or radioresources of a dedicated CORESET on the cell. The one or more first RSsmay comprise, for example, one or more first CSI-RSs and/or one or morefirst SS blocks. The one or more second RSs may comprise, for example,one or more second CSI-RSs and/or one or more second SS blocks. The oneor more configuration parameters may indicate, for example, anassociation between each of the one or more second RSs and each of oneor more PUCCH resources.

A wireless device may detect a beam failure on the cell, for example, ifa radio link quality of the one or more first RSs satisfies certaincriteria. The beam failure may occur, for example, if an RSRP and/orSINR of the one or more first RSs is less than a first threshold and/orif a BLER is greater than a first threshold. This assessment may be fora consecutive number of times based on a value provided by a higherlayer (e.g., RRC, MAC). The wireless device may initiate a BFR procedure(e.g., PUCCH-based BFR), for example, based on or in response todetecting the beam failure.

Initiating the BFR procedure may comprise selecting a selected RS, inthe one or more second RSs, for transmission of a first signal. Theselected RS may be associated with one of the one or more second RSswith radio quality greater than a second threshold. The second thresholdmay be based on an L1-RSRP, an RSRQ, a hypothetical BLER, and/or anSINR. The selected RS may be associated with a first PUCCH resource ofthe one or more PUCCH resources. The first PUCCH resource may compriseat least one channel resource. The at least one channel resource maycomprise, for example, one or more time resources and/or one or morefrequency resources.

The wireless device may trigger the transmission of the first signal viathe first PUCCH resource, for example, based on selecting the selectedRS. The first PUCCH resource may overlap, for example, with a scheduledtransmission of a second signal via a PUSCH resource of the cell. Thewireless device may drop the scheduled transmission of the secondsignal, for example, based on or in response to determining that thefirst PUCCH resource overlaps with the PUSCH resource. The wirelessdevice may perform the transmission of the first signal via the firstPUCCH resource, for example, based on dropping the scheduledtransmission.

The wireless device may monitor, for control information, a downlinkcontrol channel based on or in response to the transmission of the firstsignal. The monitoring of the downlink control channel may comprise, forexample, searching for the control information in the downlink controlchannel addressed by an identifier associated with the wireless device.The control information may be received on a dedicated CORESET. Thewireless device may complete the BFR procedure successfully, forexample, based on or in response to receiving the control information onthe dedicated CORESET.

A BFR procedure may be prioritized by, for example, using a CORESET witha high priority. A BFR procedure may be prioritized by, for example,setting a CORESET (e.g., BFR-CORESET) to have a higher priority thanother CORESETs. A BFR procedure may be prioritized, for example, byusing a CORESET, among a plurality of CORESETs, with a highest priorityfor a BFR procedure. A BFR procedure may be prioritized, for example, byusing a primary CORESET for a BFR procedure.

FIG. 23 shows an example method for a BFR procedure by a wirelessdevice. At step 2304, the wireless device may receive, from a basestation, one or more messages comprising one or more configurationparameters for a cell. The one or more configuration parameters mayindicate, for example, parameters for a BFR procedure. The parametersfor the BFR procedure may include, for example, one or more PUCCHresources for transmission of a first signal for the BFR procedure of acell. At step 2308, the wireless device may detect a beam failure andinitiate a BFR procedure for the cell. At step 2312, the wireless devicemay select a candidate beam for the BFR procedure. At step 2316, thewireless device may transmit an uplink signal (e.g., a BFR signal suchas a preamble transmitted on a PRACH resource) associated with thecandidate beam for the BFR procedure. At step 2320, the wireless devicemay monitor (e.g., with the candidate beam) a BFR CORESET for a BFRresponse (e.g., response to the BFR signal). At step 2324, the wirelessdevice may determine if the BFR CORESET overlaps in time with a secondCORESET of the cell. At step 2336, the wireless device may monitor: (i)the second CORESET of the cell with the configured beam, and (ii) theBFR CORESET with the candidate beam, for example, if the wireless devicedetermines that the BFR CORESET does not overlap in time with theanother CORESET. At step 2332, the wireless device may determine if aconfigured beam for the second CORESET of the cell is different from (ornot QCL-ed with) the candidate beam of the BFR CORESET. If the wirelessdevice determines the configured beam for the another CORESET of thecell is the same as (or QCL-ed with) the candidate beam of the BFRCORESET, at step 2336, the wireless device may monitor: (i) the secondCORESET of the cell with the configured beam, and (ii) the BFR CORESETwith the candidate beam. At step 2340, the wireless device may either(i) monitor the second CORESET of the cell with the configured beam andmonitor the BFR CORESET with the candidate beam (e.g., option 1), or(ii) stop monitoring the second CORESET of the cell and start and/orcontinue monitoring the BFR CORESET with the candidate beam (e.g.,option 2). The base station and/or the wireless device may determinewhich of option 1 or option 2 to perform. The base station may send, tothe wireless device, one or more messages indicating which of option toperform (e.g., option 1 or option 2). A selection of option 1 or option2 may be based on a predetermined rule that the base station and/or thewireless device may apply, such as based on an index (e.g., CORESETindex, BWP index, etc.), numerology, service (e.g., eMBB, URLLC, etc.),or any other indicator.

FIG. 24 shows an example method for a BFR procedure at a base station.At step 2400, the base station may transmit configuration parameters fora first CORESET of a cell and a BFR CORESET, each with different QCLassumptions (or different beams/RSs). At step 2404, the base station mayreceive an uplink signal (e.g., a BFR signal such as a preambletransmitted on a PRACH resource) associated with a candidate beam. Thecandidate beam may be a beam corresponding to a BFR procedure. At step2408, the base station may determine if the BFR CORESET overlaps in timewith the CORESET of the cell. At step 2420, the base station maytransmit: (i) a DCI via the CORESET of the cell with the configured beamand (ii) a BFR response via the BFR CORESET with the candidate beam, forexample, if the base station determines that the BFR CORESET does notoverlap in time with the CORESET of the cell. At step 2416, the basestation may determine if a configured beam for the CORESET of the cellis different from (or not QCL-ed with) the candidate beam of the BFRCORESET. If the base station determines that the configured beam for theCORESET of the cell is the same as (or QCL-ed with) the candidate beamof the BFR CORESET, at step 2420, the base station may transmit: (i) aDCI via the CORESET of the cell with the configured beam and (ii) a BFRresponse via the BFR CORESET with the candidate beam. At step 2424, thebase station may (i) transmit DCI via the CORESET of the cell andtransmit a BFR response via the BFR CORESET with the candidate beam, or(ii) stop transmitting DCI via the CORESET of the cell and transmit aBFR response via a BFR CORESET with the candidate beam.

A base station may send, to a wireless device that may receive, one ormore messages (e.g.,

RRC messages). The one or more messages may comprise one or moreconfiguration parameters. The one or more configuration parameters maycomprise beam failure recovery request configuration parameters. The oneor more configuration parameters may indicate one or more PUCCHresources for transmission of a first signal for a beam failure recoveryprocedure. The first signal may comprise a beam failure recoveryrequest. The one or more configuration parameters may indicate one ormore of: one or more first reference signals (RSs), one or more secondRSs, an association between the one or more second RSs and the one ormore PUCCH resources, and/or radio resources of a dedicated CORESET. Theone or more first RSs may comprise one or more first CSI-RSs and/or oneor more first SS/PBCH blocks. The wireless device may detect a beamfailure. The wireless device may detect the beam failure, for example,by assessing the one or more first RSs with radio quality lower than afirst threshold. The first threshold may be based on hypothetical BLER,RSRP, RSRQ, and/or SINR. The wireless device may initiate the beamfailure recovery procedure (e.g., based on detecting the beam failure).The wireless device may initiate the beam failure recovery procedure,for example, by selecting a selected RS of the one or more second RSs.The selected RS may be associated with the first PUCCH resource, and/orthe first PUCCH resource may comprise at least one channel resource. Theselected RS may have a radio quality greater than a second threshold.The second threshold may be based on L I -RSRP, RSRQ, hypothetical BLER,and/or SINR. The wireless device may trigger transmission of the firstsignal and/or determine to transmit the first signal (e.g., based ondetecting the beam failure). The wireless device may determine that afirst PUCCH resource, of the one or more PUCCH resources fortransmission of the first signal overlaps with a scheduled transmissionof one or more transport blocks via a PUSCH. Based on the determiningthat the first PUCCH resource overlaps with the scheduled transmissionof the one or more transport blocks via the PUSCH, the wireless devicemay: drop the scheduled transmission of the one or more transport blocksvia the PUSCH, and/or transmit, via the first PUCCH resources, the firstsignal. Instead of dropping the scheduled transmission of the one ormore transport blocks via the PUSCH, the wireless device may suspend thescheduled transmission of the one or more transport blocks via the PUSCH(e.g., at least until the beam failure recovery procedure issuccessfully completed). The wireless may transmit the first signal viaat least one channel resource of the first PUCCH resource. The firstsignal may be a scheduling request (SR) for the beam failure recoveryprocedure. The wireless device may monitor, for control information, adownlink control channel based on the transmitting the first signal. Themonitoring may comprise searching for the control information in thedownlink control channel addressed for an identifier associated with thewireless device. The wireless device may determine to transmit a firstSR. Based on determining that a second PUCCH resource, for transmissionof the first SR, overlaps with a second scheduling transmission of oneor more transport blocks via the PUSCH, the wireless device may: dropthe transmission of the first SR, and/or transmit, via the PUSCH, thesecond scheduled transmission of the one or more transport blocks. Thewireless device may successfully complete a beam failure recoveryprocedure based on receiving control information via a dedicatedCORESET. The wireless device may cancel a transmission of the firstsignal based on successfully completing the beam failure recoveryprocedure. The wireless device may determine that a second PUCCHresource, of the one or more PUCCH resources for transmission of thefirst signal, overlaps with a second scheduling transmission of one ormore transport blocks via the PUSCH. Based on the determining, thewireless device may suspend the second scheduling transmission of theone or more transport blocks via the PUSCH at least until the beamfailure recovery procedure is successfully completed. The wirelessdevice may transmit, after a determination that the beam failureprocedure is successfully completed, the second scheduling transmissionof the one or more transport blocks via the PUSCH. The wireless devicemay delay the scheduled transmission of the one or more transport blocksvia the PUSCH at least until successfully completing the beam failurerecovery procedure. The wireless device may cancel the first SR based onsuccessfully completing the beam failure recovery procedure. Thewireless device may keep the first SR pending, for example, based onsuccessfully completing the beam failure recovery procedure.

A base station may send, to a wireless device that may receive, one ormore messages comprising configuration parameters that indicate one ormore of: a first reference signal (RS) of a first channel, and a secondRS of a second channel. The wireless device may select a channel (e.g.,a selected channel) from the first channel and the second channel, forexample, based on one or more of: a channel configuration for a beamfailure recovery procedure, a first channel and the second channeloverlapping in at least one symbol, and first antenna ports of the firstRS not being quasi-colocated with the second antenna ports of the secondRS. The base station may send, to the wireless device that may receive,downlink control information via the selected channel. The wirelessdevice may transmit, via the selected channel, an uplink signal. Thewireless device may apply a selected RS of the selected channel for thefirst channel and the second channel.

FIG. 25 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 122A and/or 122B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 2500 may include one ormore processors 2501, which may execute instructions stored in therandom access memory (RAM) 2503, the removable media 2504 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive2505. The computing device 2500 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 2501 andany process that requests access to any hardware and/or softwarecomponents of the computing device 2500 (e.g., ROM 2502, RAM 2503, theremovable media 2504, the hard drive 2505, the device controller 2507, anetwork interface 2509, a GPS 2511, a Bluetooth interface 2512, a WiFiinterface 2513, etc.). The computing device 2500 may include one or moreoutput devices, such as the display 2506 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 2507, such as a video processor. There mayalso be one or more user input devices 2508, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device2500 may also include one or more network interfaces, such as a networkinterface 2509, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 2509 may provide aninterface for the computing device 2500 to communicate with a network2510 (e.g., a RAN, or any other network). The network interface 2509 mayinclude a modem (e.g., a cable modem), and the external network 2510 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 2500 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 2511, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 2500.

The example in FIG. 25 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2500 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2501, ROM storage 2502, display 2506, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 25.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, one or more configuration parameters that indicate one or morephysical uplink control channel (PUCCH) resources for transmission of afirst signal for a beam failure recovery procedure; determining, basedon a detected beam failure, to transmit the first signal; determiningthat a first PUCCH resource, of the one or more PUCCH resources fortransmission of the first signal, overlaps with a scheduled transmissionof one or more transport blocks via a physical uplink shared channel(PUSCH); and based on the determining that the first PUCCH resourceoverlaps with the scheduled transmission of the one or more transportblocks via the PUSCH: dropping the scheduled transmission of the one ormore transport blocks via the PUSCH; and transmitting, via the firstPUCCH resource, the first signal.
 2. The method of claim 1, wherein thefirst signal is a scheduling request (SR) for the beam failure recoveryprocedure.
 3. The method of claim 1, further comprising: determining totransmit a first scheduling request (SR); based on determining that asecond PUCCH resource, for transmission of the first SR, overlaps with asecond scheduled transmission of one or more transport blocks via thePUSCH: dropping the transmission of the first SR; and transmitting, viathe PUSCH, the second scheduled transmission of the one or moretransport blocks.
 4. The method of claim 1, wherein the one or moreconfiguration parameters further indicate: one or more first referencesignals (RSs); one or more second RSs; an association between the one ormore second RSs and the one or more PUCCH resources; and radio resourcesof a dedicated control resource set (CORESET).
 5. The method of claim 4,further comprising selecting an RS, from the one or more second RSs, forthe beam failure recovery procedure, wherein: the selected RS isassociated with the first PUCCH resource; and the first PUCCH resourcecomprises at least one channel resource.
 6. The method of claim 1,further comprising: based on determining that a second PUCCH resource,of the one or more PUCCH resources for transmission of the first signal,overlaps with a second scheduled transmission of one or more transportblocks via the PUSCH: suspending the second scheduled transmission ofthe one or more transport blocks via the PUSCH at least until the beamfailure recovery procedure is successfully completed.
 7. The method ofclaim 6, further comprising: transmitting, after a determination thatthe beam failure procedure is successfully completed, the secondscheduled transmission of the one or more transport blocks via thePUSCH.
 8. A method comprising: receiving, by a wireless device, beamfailure recovery request configuration parameters that indicate one ormore physical uplink control channel (PUCCH) resources; detecting a beamfailure; determining that a first PUCCH resource, of the one or morePUCCH resources, for a transmission of a beam failure recovery request,overlaps with a scheduled transmission of one or more transport blocksvia a physical uplink shared channel (PUSCH); and based on thedetermining: dropping the scheduled transmission of the one or moretransport blocks via the PUSCH; and transmitting, via the first PUCCHresource, the beam failure recovery request.
 9. The method of claim 8,wherein the beam failure recovery request is a scheduling request (SR)for a beam failure recovery procedure.
 10. The method of claim 8,further comprising: initiating, based on the detecting the beam failure,a beam failure recovery procedure.
 11. The method of claim 8, furthercomprising: determining to transmit a first scheduling request (SR);based on determining that a second PUCCH resource, for transmission ofthe first SR, overlaps with a second scheduled transmission of one ormore transport blocks via the PUSCH: dropping the transmission of thefirst SR; and transmitting, via the PUSCH, the second scheduledtransmission of the one or more transport blocks.
 12. The method ofclaim 8, wherein the beam failure recovery request configurationparameters further indicate: one or more first reference signals (RSs);one or more second RSs; an association between the one or more secondRSs and the one or more PUCCH resources; and radio resources of adedicated control resource set (CORESET).
 13. The method of claim 8,further comprising: based on determining that a second PUCCH resource,of the one or more PUCCH resources, for the transmission of the beamfailure recovery request, overlaps with a second scheduled transmissionof one or more transport blocks via the PUSCH: suspending the secondscheduled transmission of the one or more transport blocks via the PUSCHat least until a beam failure recovery procedure is successfullycompleted.
 14. The method of claim 13, further comprising: transmitting,after a determination that the beam failure recovery procedure issuccessfully completed, the second scheduled transmission of the one ormore transport blocks via the PUSCH.
 15. A method comprising: receiving,by a wireless device, one or more configuration parameters that indicateone or more physical uplink control channel (PUCCH) resources fortransmission of a first signal; determining, based on a detected afailure, to transmit the first signal; based on determining that a firstPUCCH resource, of the one or more PUCCH resources for transmission ofthe first signal, overlaps with a scheduled transmission of one or moretransport blocks via a physical uplink shared channel (PUSCH):suspending the scheduled transmission of the one or more transportblocks via the PUSCH; and transmitting, via the first PUCCH resource,the first signal.
 16. The method of claim 15, wherein the first signalis a scheduling request (SR).
 17. The method of claim 15, furthercomprising: initiating, based on the detecting the failure, a failurerecovery procedure.
 18. The method of claim 15, further comprising:determining to transmit a first scheduling request (SR); based ondetermining that a second PUCCH resource, for transmission of the firstSR, overlaps with a second scheduled transmission of one or moretransport blocks via the PUSCH: dropping the transmission of the firstSR; and transmitting, via the PUSCH, the second scheduled transmissionof the one or more transport blocks.
 19. The method of claim 15, whereinthe one or more configuration parameters further indicate: one or morefirst reference signals (RSs); one or more second RSs; an associationbetween the one or more second RSs and the one or more PUCCH resources;and radio resources of a dedicated control resource set (CORESET). 20.The method of claim 15, further comprising: based on determining that asecond PUCCH resource, of the one or more PUCCH resources for thetransmission of the first signal, overlaps with a second scheduledtransmission of one or more transport blocks via the PUSCH: dropping thesecond scheduled transmission of the one or more transport blocks viathe PUSCH; and transmitting, via the second PUCCH resource, the firstsignal.